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 skills/jartan-llc/grimoire/recursive-executionnpx skills add Jartan-LLC/grimoire --skill recursive-executiongit clone --depth 1 https://github.com/Jartan-LLC/grimoireWrote 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/skills/jartan-llc/grimoire/recursive-execution)<a href="https://agentmods.dev/skills/jartan-llc/grimoire/recursive-execution"><img src="https://agentmods.dev/badge/skills/jartan-llc/grimoire/recursive-execution.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.00022 | $0.00559 |
| Opus 5 | $0.00011 | $0.00280 |
| Sonnet 5 | $0.00004 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
recursive-execution 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recursive Execution
Agent Constraints
These apply to ALL agents in the recursive tree:
- No worktree isolation. Never use
isolation: "worktree". Worktree agents work in a copy -- files get discarded on cleanup. - No background agents. Never use
run_in_background: true. Background dispatch triggers worktree isolation. Use foreground Agent calls -- send parallel agents in a single message for concurrency. - Fix delegation. Simple fixes (unused import, missing return) directly. Logic fixes (bugs, structural merges) via a
recursive-implementerscoped to affected files with findings in the prompt. - Failure escalation. When a child agent fails: parent retries (max 2), restructures (split differently), or escalates to its own parent. Handle failures at the lowest level that has enough context to fix them.
Wave Execution
Waves execute sequentially. Within each wave, agents run in parallel.
Wave barrier: all agents must complete before running tests or starting the next wave. Send all wave agents as foreground calls in a single message when possible. Sequential dispatch is acceptable when needed.
Typical structure:
- Wave 0: Contracts + setup (uses
recursive-implementer) - Wave 1+: Implementation modules (parallel
recursive-implementeragents) - Final wave: Integration tests + documentation
Adapting mid-flight: the orchestrator may add missing deps, adjust types, reorder/merge modules, fix structural issues between waves, and adjust scope boundaries.
Review-Fix Evaluation
After each wave, spawn a recursive-reviewer scoped to the wave's output:
Post-Wave 0: review contracts for richness -- are interfaces complete enough for downstream modules? Fix gaps directly.
Post-implementation waves: review for bugs, structural artifacts, cross-module consistency. Fix Critical findings via implementer agents (max 2 rounds). Note Important findings.
Post-final wave: full codebase review. Fix Critical. Verify README.md and CHANGELOG.md exist -- create via implementer if missing.
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 · 54 lines · 22 tokens per session scan A 3757e50c77ff
recursive-execution is a skill published in the GitHub repository Jartan-LLC/grimoire (2 stars, last pushed 17d ago), licensed MIT. It adds 22 tokens to every session and 559 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 skills, from other repositories
tastemaker
Generate genuinely beautiful, on-brand UI instead of generic "AI slop" — use whenever the user asks to build, design, style, or improve a UI, landing page, dashboard, app screen, or component, whenever a PRD/spec needs a design pass before implementation, whenever the user pastes reference images/Pinterest/Dribbble…
fde
Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a…
kubernetes-skill
Prevent Kubernetes hallucinations by diagnosing and fixing failure modes: insecure workload defaults, resource starvation, network exposure, privilege sprawl, fragile rollouts, and API drift. Use when generating, reviewing, refactoring, or migrating manifests, Helm charts, Kustomize overlays, cluster policies, and…
image-to-psd
将一张或多张图片转换为经过严格质量校验的分层 PSD；可独立运行，也可使用 image2editable 的 Host、Local 或本地服务 Agent。输出修复背景、独立透明视觉组件和可编辑 Photoshop 文字图层。仅支持图片输入，不用于 PDF 或 PPTX。.
img2mo-learn
Learn reusable 2D motion-generation knowledge from user-specified action resources with /img2mo-learn . Use when the user provides videos, extracted frame sequences, spritesheets, Spine assets, generated outputs, failed attempts, or reference motion folders and wants to summarize animation timing, pose beats, style…
img2mo-std
Standardize a 2D animation baseline image with /img2mo-std xxx.png/pos. Use when preparing a character, creature, prop, or weapon baseline before motion generation, especially if the source image is too large, tightly cropped, lacks transparent action margin, has a white background, or later walk/attack/idle frames…