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 skills add Jartan-LLC/grimoire --skill recursive-planninggit 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-planning)<a href="https://agentmods.dev/skills/jartan-llc/grimoire/recursive-planning"><img src="https://agentmods.dev/badge/skills/jartan-llc/grimoire/recursive-planning.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.1 | $0.00028 | $0.00643 |
| Opus 5 | $0.00014 | $0.00321 |
| Sonnet 5 | $0.00006 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
recursive-planning 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 7d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recursive Planning
Decomposition Process
- Survey -- greenfield or existing? For existing: read README, types, error classes, test setup, conventions. These are constraints.
- Identify domains -- genuinely different kinds of work (parsing vs querying vs aggregating vs formatting)
- Map dependencies -- which domains need outputs from others? Dependencies flow through interfaces only.
- Assign waves -- no dependencies -> Wave 1. Depends on Wave 1 -> Wave 2. Wave 0 is always contracts/setup. Integration is final wave.
- Assign scopes -- each module gets a directory or file set. Zero overlap between parallel modules.
- Specify conventions -- language, test framework, type system, DI pattern, path handling, package manager
- Plan deliverables -- README, CHANGELOG,
--version, runtime version access, coverage config
Module Split Criteria
See recursive-development skill for split principle and examples. Goal: natural, best-practice file structure.
Contract Guidance
Wave 0 agent designs contracts. The plan specifies what they should cover:
- Enumerate capabilities -- list all operations/formats/modes, not just common ones
- Error handling -- "Parsers yield Record | ParseError" not "Parsers raise on bad input"
- Batch interfaces -- "Aggregator takes list[AggregationSpec]" not single-item
- Injectable I/O -- "Formatters accept a write callable"
- Types only -- contracts file has protocols, dataclasses, enums, type aliases, constants. No callable stubs.
- Exception hierarchy -- base exception + subtypes per failure domain
- Logging -- modules use named loggers, CLI configures at entry point
For existing projects: extend existing contracts, match established patterns.
Wave Plan Format
Save to .claude/workspace/wave-plan-<project-name>.md.
## Implementation Plan -- `<name>` <description>
### Issue Summary
### Language & Conventions
### Language-Specific Standards
(Standards shaped to this project's language and domain -- specifics that all agents must follow.
These go beyond generic conventions. Think about what a senior developer in this language would
insist on in a code review.)
### Existing Patterns (existing projects only)
### Chosen Approach
## Wave 0: Contracts & Project Setup
## Wave 1: <name> (N parallel)
### Module A -- Owns: <scope>, Responsibility: <one line>
## Wave 2: <name>
### Module C -- Owns: <scope>, Depends on: <interfaces>, Responsibility: <one line>
## Wave N: Integration + Documentation (README.md, CHANGELOG.md)
## File Ownership Map
### Complexity: Simple | Moderate | Complex
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.
- 7d ago First seen · 63 lines · 28 tokens per session scan A 0679a747c146
recursive-planning is a skill published in the GitHub repository Jartan-LLC/grimoire (2 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 643 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
A skill that reconstructs images as editable, layered Photoshop files. It separates the repaired background, visual components, and text into layers instead of leaving the page as one flat image.
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…