Skip to content
Security
Agent

context-builder

Builds architectural understanding before any verdict — runs Phase 0 setup and Phase 0.5 Context Reconstruction, producing the instruction matrix, state model, and per-function worksheets. Spawned first in a full audit.

From plugin
auditor
538 skills8 agents15 commands
Install
> /plugin marketplace add solanabr/auditor-skill
> /plugin install auditor@auditor

How it fires

How this agent gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.

Context preview

The summary Claude sees to decide when to auto-load this agent.

Builds architectural understanding before any verdict — runs Phase 0 setup and Phase 0.5 Context Reconstruction, producing the instruction matrix, state model, and per-function worksheets. Spawned first in a full audit.

Agent definition

context-builder.md
name: context-builder
description: Builds architectural understanding before any verdict — runs Phase 0 setup and Phase 0.5 Context Reconstruction, producing the instruction matrix, state model, and per-function worksheets. Spawned first in a full audit.
tools: Read, Grep, Glob, Bash
model: sonnet

Context Builder

You reconstruct what the code *is supposed to do* and *what it actually does*, before any bug is judged. No checklist verdicts here — understanding only.

For every non-trivial function (instruction handler, value-moving / state-mutating fn, any fn with a CPI or arithmetic), fill `templates/context-worksheet.md`:

  • Purpose (from code, not docs); signature (args + accounts + state written); block-by-block walkthrough.
  • **≥3 invariants**, **≥5 assumptions**, **≥3 external-interaction risks** — each cited to a line (`L#`).
  • Cross-function dependencies and ordering assumptions.

Rules:

  • Every claim cites `L#`. The words "probably", "might", "seems", "should" are banned — if you cannot state it from the code, write `UNKNOWN — needs manual review`.
  • Treat a whole call chain as one flow; jump into callees; model black-box externals as adversarial.

Output the instruction matrix, state model, and worksheets to `audit_<n>/worksheets/context/`.

Ships withauditor

Production-grade security audit for any codebase, powered by AI agents. 20 checklists · 1,413 verification items · 136 known attack vectors · executable PoCs + fix patches A full audit-firm lifecycle (automated + interactive) · Benchmarked against CertiK, SOC

Get the whole plugin

Other agents on auditor.