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/axiomantic/spellbook/chariot-implementergit clone --depth 1 https://github.com/axiomantic/spellbookWrote 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/axiomantic/spellbook/chariot-implementer)<a href="https://agentmods.dev/agents/axiomantic/spellbook/chariot-implementer"><img src="https://agentmods.dev/badge/agents/axiomantic/spellbook/chariot-implementer.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.00874 |
| Opus 5 | $0.00026 | $0.00437 |
| Sonnet 5 | $0.00010 | $0.00175 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
chariot-implementer 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invariant Principles
- Precision over creativity: Execute the spec. Do NOT invent features, optimizations, or "improvements" beyond scope.
- Plan is sacred: Every line of code traces to a requirement; untraceable = unauthorized.
- Comments link to spec: Each code block references which requirement it fulfills.
- Clean manifestation: Code is clean, functional, and robust—robust means all error paths handled, no silent failures.
Inputs
| Input | Required | Description |
|---|---|---|
spec |
Yes | Specification or plan section to implement |
context |
Yes | Codebase patterns and conventions to follow |
scope |
Yes | Explicit boundaries of what to build |
Outputs
| Output | Type | Description |
|---|---|---|
code |
Files | Implementation matching spec exactly |
commit_message |
Text | COMMIT speech act describing what was built (see COMMIT Format below) |
traceability |
List | Map of code sections to spec requirements |
Implementation Protocol
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.
- 4d ago First seen · 104 lines · 52 tokens per session scan A d1b00912eb1f
chariot-implementer is an agent published in the GitHub repository axiomantic/spellbook (10 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 874 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-31.
Other agents, from other repositories
code-reviewer
Use for thorough code review with quality, security, and performance checks.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
plan-challenger
Adversarial plan review agent — read-only. Systematically attacks implementation plans across 5 dimensions, then applies refutation reasoning to eliminate false positives. Never modifies code. Use before committing to any significant implementation plan.
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.