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.
git clone --depth 1 https://github.com/realgarit/fable-batonWrote 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/realgarit/fable-baton/architect)<a href="https://agentmods.dev/agents/realgarit/fable-baton/architect"><img src="https://agentmods.dev/badge/agents/realgarit/fable-baton/architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/realgarit/fable-baton/architect"><img src="https://agentmods.dev/badge/agents/realgarit/fable-baton/architect.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00054 | $0.00410 |
| Opus 5.5 | $0.00022 | $0.00164 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 31 lines · 54 tokens per session scan A f2ee537057d5
architect is an agent published in the GitHub repository realgarit/fable-baton (27 stars, last pushed 4d ago), licensed MIT. It adds 54 tokens to every session and 410 once invoked, about $0.0002 per session on Opus 5.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
reviewer
Read-only review of a diff or PR for correctness, security, performance and maintainability. Returns path:line findings and a verdict. Use before merging a change.
code-resolver
Re-checks prior findings after a code fix. Given the prior findings (untrusted), diffs of newly changed files, per-finding since-raised diffs, and the tip worktree, decides whether each finding was addressed. Not for general questions.
issue-validator
Re-validates a single finding produced by another reviewer with fresh context. Returns valid / invalid / unsure. Triggered by /mumei:compose after the 3 reviewers complete (spec-compliance / security / adversarial) — invoked once per finding in parallel for severity=HIGH/CRITICAL findings. Filters false positives…
refiner
A review assistant that examines why an evaluator marked code as failed or conditional and proposes specific fixes without changing the code itself.
critic
Adversarial verifier. Use PROACTIVELY before claiming a nontrivial change is done, fixed, or passing — give it the claim plus the relevant diff/paths and it attempts to refute the claim with evidence.
qc-lead
QC team lead — the truth audit. Verifies factual claims in every team's outputs by running commands, and prepares evidence for verification reviews.