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/superduke/ganvil/plannpx skills add superduke/ganvil --skill plangit clone --depth 1 https://github.com/superduke/ganvilWrote 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/superduke/ganvil/plan)<a href="https://agentmods.dev/skills/superduke/ganvil/plan"><img src="https://agentmods.dev/badge/skills/superduke/ganvil/plan.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.00058 | $0.00382 |
| Opus 5 | $0.00029 | $0.00191 |
| Sonnet 5 | $0.00012 | $0.00076 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
plan 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.
What it actually says
Ganvil Plan — Product Specification Generator
Generate a comprehensive product specification from a brief description, without building the application.
What to Do
- Create the
ganvil-artifacts/directory if it doesn't exist. - Delegate to the planner agent with the user's description:
$ARGUMENTS- If the current directory contains an existing project (has
package.json,Cargo.toml,requirements.txt,go.mod, etc.), include context: "Note: there is an existing codebase in the working directory. Analyze it and plan to extend/modify it rather than building from scratch."
- If the current directory contains an existing project (has
- The planner will:
- Classify the project type (FRONTEND / BACKEND / FULLSTACK)
- Generate a complete product specification
- Define a visual design language (for frontend projects)
- Decompose the work into sprints with testable acceptance criteria
- The output will be written to
ganvil-artifacts/spec.md - After planning is complete, summarize:
- Project type classification
- Number of sprints planned
- Key features identified
- Highlight any particularly ambitious or AI-powered features
Usage
/ganvil:plan A collaborative whiteboard tool with real-time editing
This will generate a full spec in ganvil-artifacts/spec.md that can later be used with /ganvil:build or manually implemented.
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 · 39 lines · 58 tokens per session scan A db074c72c963
plan is a skill published in the GitHub repository superduke/ganvil (3 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 382 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 skills, from other repositories
review
Reviews code changes for concrete bugs with P0-P2 prioritized findings. Uses parallel architectural and implementation reviewers, then validates findings to remove false positives. Use when reviewing a caller-supplied diff, branch, staged changes, file set, or pull request, and use fix mode with caller-supplied…
extracting-requirements
Use when starting an iterative-development run on human spec collateral — reads the spec, produces per-epic requirement files with proof obligations and behavior scenario cards with stable IDs.
iterative-development
Use when implementing a project with a large, comprehensive, or ambiguous spec — extracts requirements with proof obligations, defines a walking skeleton with its first journey scenario, then loops through audited sprints that continuously build a behavior evidence corpus. Completion means passing evidence, not just…
design
Create a doc-as-code design package from a PRD or SPEC. Conditionally generates C4 diagrams (Context/Container/Component), sequence diagrams, ER diagram + Data Dictionary, OpenAPI 3.0, AsyncAPI 3.0, ADRs, domain glossary, state diagrams, and deployment view as Mermaid-rendered Markdown files. Use when PM mentions…
tasks
Decompose a PLAN / SPEC / FEAT / BUG / DEBT / CHORE into atomic TASK-NNN items ready for the implement flow, via a clean-context subagent. Use when PM mentions "create tasks", "generate TASKs", "break down into tasks", "tasks from PLAN", "break this into tasks", "декомпозиция", "сделай таски", or any request to…
scoping-the-simplest-core
Use when turning extracted requirements into a roadmap — selects the walking skeleton iteration with its first journey scenario, orders remaining work into follow-on iterations, and applies story splitting when ACs have different dependency profiles.