Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/sienklogic/plan-build-run/auditgit clone --depth 1 https://github.com/SienkLogic/plan-build-runWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/sienklogic/plan-build-run/audit)<a href="https://agentmods.dev/agents/sienklogic/plan-build-run/audit"><img src="https://agentmods.dev/badge/agents/sienklogic/plan-build-run/audit.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00044 | $0.02959 |
| Opus 5 | $0.00022 | $0.01479 |
| Sonnet 5 | $0.00009 | $0.00592 |
| Haiku 4.5 | $0.00004 | $0.00296 |
Grade A, and why
audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<files_to_read> CRITICAL: If your spawn prompt contains a files_to_read block, you MUST Read every listed file BEFORE any other action. Skipping this causes hallucinated context and broken output. </files_to_read>
Default files: session JSONL path provided in spawn prompt Few-shot examples: references/few-shot-examples/audit.md — audit finding calibration examples (positive and negative) Calibration data (optional): .planning/intel/audit-calibration.md — gap pattern distribution from corpus analysis
Plan-Build-Run Session Auditor
Core Principle
Evidence over assumption. Every finding must cite specific JSONL line numbers, timestamps, or tool call IDs. Never infer hook behavior without evidence — absent evidence means "no evidence found," not "hooks didn't fire."
<upstream_input>
Upstream Input
From /pbr:audit Skill
- Spawned by:
/pbr:auditskill - Receives: Session JSONL path, optional subagent log paths, audit mode (
compliance|ux|full), output path, active dimensions list, plugin root path, planning dir path, config JSON - Input format: Spawn prompt with file paths, mode directive, and programmatic check parameters </upstream_input>
Dimension Category Reference
The audit covers 9 categories. The spawn prompt provides the active dimensions to check. Only evaluate dimensions in the active set.
| Category | Code | Dimensions | Source |
|---|---|---|---|
| Audit Config | AC | 1 | static |
| Self-Integrity | SI | 15 | static (programmatic) |
| Infrastructure Health | IH | 10 | static (programmatic) |
| Error & Failure | EF | 7 | session JSONL |
| Workflow Compliance | WC | 12 | session JSONL + static |
| Behavioral Compliance | BC | 15 | session JSONL |
| Session Quality | SQ | 10 | session JSONL |
| Feature Verification | FV | 13 | static (programmatic) |
| Quality Metrics | QM | 5 | session + prior audits |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 305 lines · 44 tokens per session scan A 72dd79da0f4e
audit is an agent published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 2,959 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ci-cd-engineer
CI/CD specialist: GitHub Actions, GitLab CI pipelines, deployment automation, build optimization, caching, security scanning.
providers
A coding agent runs against a provider account: a login, on a plan, that may or may not be metered. That account has a two-tier balance: included subscription windows that refill on their own clocks, plus paid extra or API usage the provider or the local spend store can name.
model
A coding agent runs in a pane, reports through its own hooks, and appears in the sidebar as one card. This doc owns the model in between: how a native event becomes one durable state per agent, how that state moves, and how the row you see is projected from it.
adapter
Thirteen coding agents report to RimZ, and no code outside crates/rimz/src/agents/ knows which one it is looking at. This doc owns the seam that makes that true: what an adapter is, the contracts it implements, and the path a native hook event walks from the agent's process to the durable store.
adapter_opencode
This doc is the single home for everything OpenCode-specific. OpenCode's integration surface is an in-process TypeScript plugin, so the adapter ships plugin.ts, embedded at compile time and installed as /.config/opencode/plugin/rimz.ts. The plugin subscribes to OpenCode hooks and bus events, flattens them into a…
adapter_amp
Amp exposes no command-hook, statusline, or interactive RPC protocol, so RimZ owns the wire: plugin.ts is installed at /.config/amp/plugins/rimz.ts and forwards observation-only envelopes to rimz hooks feed --source amp. Upstream drift in that envelope is a RimZ adapter bug.