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/bonigarcia/context-engineering/reviewergit clone --depth 1 https://github.com/bonigarcia/context-engineeringWhat 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.00000 | $0.00033 |
| Opus 5 | $0.00000 | $0.00016 |
| Sonnet 5 | $0.00000 | $0.00007 |
| Haiku 4.5 | $0.00000 | $0.00003 |
Grade A, and why
reviewer 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.
What it actually says
Reviewer checklist
- Confirm the scoring rule matches the specified formula.
- Confirm invalid numeric score components are rejected.
- Confirm the example stays intentionally small and focused.
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 · 6 lines · 0 tokens per session scan A 83c831b4b7ef
reviewer is an agent published in the GitHub repository bonigarcia/context-engineering (132 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 33 tokens. 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
conductor
You are the COO of your simulated office. You own EVERY SINGLE INQUIRY — the first prompt and every follow-up prompt in every session. No request bypasses you. You receive all tasks, assess scope, and distribute work to the appropriate team. Trivial queries → delegate to @quick. Skill triggers → route to the…
mesh-wrapper
Lateral agent communication protocol with A2A semantics. Enables direct peer-to-peer communication, task delegation, event subscriptions, knowledge caching, conflict resolution, rate limiting, and persistent cross-agent impact awareness for multi-agent coordination at any scale.
scout
Use this agent when starting any substantial task (3+ steps, multi-file work, or complex workflows). It runs silently in the background via the Task tool with runinbackground: true, monitoring for repeatable patterns, skill gaps, and agent opportunities without interrupting active work. Surface its findings at natural…
agents-index
Agent routing table and deployment rules. Not an executable agent - serves as documentation and reference for the agent system.
alignment-monitor
Skill-agent alignment guardian. Monitors for orphan skills, dead references, and routing gaps. Ensures every skill file is reachable via index routing and every agent has properly assigned skill domains. Use when: Weekly alignment check (Monday cleanup integration) New skill or agent is created System health check…
builder
Use this agent when you need to write, implement, or refactor production-ready code across the full stack. Trigger this agent when: (1) building new features or components, (2) implementing specifications from design or architecture, (3) writing tests for new or existing code, (4) refactoring code with test coverage…