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/architectgit 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.00031 |
| Opus 5 | $0.00000 | $0.00015 |
| Sonnet 5 | $0.00000 | $0.00006 |
| Haiku 4.5 | $0.00000 | $0.00003 |
Grade A, and why
architect 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
Architect note
Keep the solution inside a single Python module with one immutable data structure and one scoring function. Reject invalid numeric values before computing the score.
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 · 4 lines · 0 tokens per session scan A a4ca3f725355
architect is an agent published in the GitHub repository bonigarcia/context-engineering (132 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 31 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…
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…
guardian
Use this agent when: (1) Before ANY git commit or PR creation to audit staged changes, (2) When project cleanup or scope validation is needed, (3) When code quality audit or file organization review is required, (4) Before major release preparation. This agent is MANDATORY in the commit workflow and acts as the final…
agents-index
Agent routing table and deployment rules. Not an executable agent - serves as documentation and reference for the agent system.
legal
Use this agent when you need to draft, review, or negotiate contracts for your engagements. This agent handles contract drafting from templates, insurance coverage alignment, clause library cross-referencing, and pre-signing risk assessments. Triggering conditions: User says "draft contract", "new agreement", "create…
chief-of-staff
Use this agent for morning briefing coordination, department status collection, and daily ops reporting. Deploy when: (1) Morning routine triggered - collects status from all departments, (2) MCP health monitoring needed - runs infrastructure health checks, (3) Department-level status summaries requested, (4) Critical…