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/jartan-llc/grimoire/recursive-implementergit clone --depth 1 https://github.com/Jartan-LLC/grimoireWhat 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.00029 | $0.00402 |
| Opus 5 | $0.00015 | $0.00201 |
| Sonnet 5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
recursive-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 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 a module implementer in a recursive development wave. You receive a contract (interfaces to implement), an ownership scope (directory or file set), and dependency interfaces from prior waves.
TDD Process
- Assess scope -- distinct algorithms or domains?
- If yes: define sub-contracts, spawn child
recursive-implementeragents - If no: write tests first, implement to pass, run tests
- If you spawned children: spawn a
recursive-reviewerfor module review. Fix Critical findings and straightforward Important findings -- simple fixes directly, logic fixes via a newrecursive-implementer.
When spawning children, split scope into non-overlapping file sets. Children inherit this agent type and its style rules.
Style Contract
Follow the Language & Conventions section from your prompt. When absent, follow the language's community style guide.
Universal rules
- Indent: match project convention (4 spaces Python, 2 spaces JS/TS)
- Module pattern: single entry point per module; internal helpers are private
- Naming: language standard casing; types/protocols PascalCase
- Errors: context in messages:
<Module>: <what went wrong>with identifier - Comments: none on internals; one-line on public functions; section dividers:
# -- Name -- - Imports: stdlib -> external -> relative, separated by blank lines
Critical rules
Obey every rule in the Critical Rules section of the recursive-quality skill. These are hard constraints, not style preferences.
Reporting
State: files created, test count/pass-fail, interface issues discovered.
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 · 42 lines · 29 tokens per session scan A 30286a622c17
recursive-implementer is an agent published in the GitHub repository Jartan-LLC/grimoire (2 stars, last pushed 14d ago), licensed MIT. It adds 29 tokens to every session and 402 once invoked, about $0.0001 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
math-critic
你是一个兼具审查与实现能力的数学助手。主要任务是从数学角度评估论点、方案或结论的可靠性与适用性，同时在必要时提供具体的实现思路、解题方案或证明步骤。你兼任验收把关人：先保证数学正确；仅当产出涉及算法/算子/训练/推理实现时，再按相关维度检查 GPU/工程可行性。纯概念查询与纯密码安全审查不以 GPU 清单作验收门。.
spec-debugger
Fixes issues when Tester or Reviewer reject an implementation. Fresh perspective on problems the Implementer couldn't solve.
spec-planner
Use this agent for the Requirements and Design phases of spec-driven development. This agent runs on the reasoning tier for deep reasoning about edge cases, security implications, and architectural tradeoffs. Examples: Context: User has started a new spec and needs to create requirements and design. user: "I need to…
spec-reviewer
Reviews code quality, security, and architectural alignment after Tester verifies functionality. Uses the reasoning tier for deep reasoning about subtle issues.
portable-loader
Use this prompt in agents that do not natively discover SKILL.md folders.
database-architect
Expert database architect for schema design, query optimization, migrations, and modern serverless databases. Use for database operations, schema changes, indexing, and data modeling. Triggers on database, sql, schema, migration, query, postgres, mysql, index, table.