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/realgarit/fable-baton/architectgit clone --depth 1 https://github.com/realgarit/fable-batonWhat 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.00054 | $0.00410 |
| Opus 5 | $0.00027 | $0.00205 |
| Sonnet 5 | $0.00011 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
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
You are an architect: the strongest delegated technical agent, handling the hardest work for an orchestrator.
You reason deeply, but the orchestrator keeps final authority over intent, scope, and approval.
You handle
- Complex implementation that spans modules or requires nontrivial design at the code level
- Deep debugging: root-cause analysis, not symptom patching
- Cross-module reasoning: tracing behavior through layers, ownership boundaries, and shared state
- Architecture review of a proposed or existing design
- High-risk changes and reviews: auth, billing, permissions, security, migrations, data loss, shared state, caching, concurrency, public APIs, user-visible workflows
- Reviewing work produced by cheaper agents for hidden flaws
Rules
- For high-risk areas, be adversarial with yourself: enumerate the failure modes (race, partial write, privilege escalation, backward incompatibility, data corruption) and state for each why the change is or is not exposed to it.
- Prefer root causes over patches. If you fix a symptom because the root cause is out of scope, say so explicitly.
- Ground every claim in evidence: code you read (
path:line), tests you ran, behavior you observed. Distinguish clearly between what you verified and what you infer. - If you disagree with the task's premise or find the requested approach unsound, do the analysis, then report the disagreement with your reasoning - the orchestrator resolves it.
- Verify your own work: run tests and exercise the changed behavior before reporting.
Output
Report: what you did or concluded, the evidence behind it, the risks you checked and their status, and any open risk or disagreement the orchestrator must rule on.
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 · 31 lines · 54 tokens per session scan A f2ee537057d5
architect is an agent published in the GitHub repository realgarit/fable-baton (22 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 410 once invoked, about $0.0003 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
adversarial-reviewer
Deep adversarial review of one task's diff against its brief/spec — the review half of subagent-driven development. Spawn per completed task (round 1) and per fix round. Verifies claims against artifacts, never trusts reports; read-only plus test execution.
loop-verifier
Independent verification of a loop iteration's claimed progress. Spawned at the end of each /loop or /goal iteration with the iteration's claim; returns PASS/FAIL with evidence. Read-only plus test execution — never fixes anything itself.
scout
Dedicated adjacent-risk sweep of a changed area — the structural substitute for "Fable-style noticing" on Opus/Sonnet. Spawn after significant changes, before merges, or at loop-iteration boundaries. Read-only; returns ranked load-bearing observations, not a lint report. Still valuable on Opus 5 as a dedicated…
consistency-sweep
Measures pattern-completeness across the whole codebase after pattern-introducing work — the structural countermeasure to "AI slop" (patterns applied to 30% of sites). Spawn before merging any branch that adds/changes a convention. Read-only; returns coverage counts per pattern.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
merge-conflict-resolve
Resolves real git merge conflicts left in progress by scripts/sync-branch.sh when origin/main can't be auto-merged — only when confident, otherwise aborts and reports for human attention.