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/maxritter/pilot-shell/build-reviewgit clone --depth 1 https://github.com/maxritter/pilot-shellWhat 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.00029 | $0.01968 |
| Opus 5 | $0.00015 | $0.00984 |
| Sonnet 5 | $0.00006 | $0.00394 |
| Haiku 4.5 | $0.00003 | $0.00197 |
Grade A, and why
build-review 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 109 lines · 29 tokens per session scan A 3c223b81f86d
build-review is an agent published in the GitHub repository maxritter/pilot-shell (2,063 stars, last pushed yesterday), with no licence file. It adds 29 tokens to every session and 1,968 once invoked, about $0.0001 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
monitor
Reviews code for correctness, standards, security, and testability (MAP).
evaluator
Evaluates solution quality and completeness (MAP).
research-agent
Heavy codebase reading with compressed output. Use PROACTIVELY before Actor implementation to gather context without polluting implementation context.
reviewer
Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad philosophical invariants. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized…
designer
Designs the actual screens for a SpecManager feature as a single self-contained HTML file — high-fidelity, stacked mockups grounded in ./docs/DESIGN.md, with formatted explanatory notes between each screen. Writes via the createdesignbrief MCP tool.
planner
Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.