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 softspark/ai-toolkit --skill prd-to-plangit clone --depth 1 https://github.com/softspark/ai-toolkitWrote 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/softspark/ai-toolkit/prd-to-plan)<a href="https://agentmods.dev/skills/softspark/ai-toolkit/prd-to-plan"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/prd-to-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/softspark/ai-toolkit/prd-to-plan"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/prd-to-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.01214 |
| Opus 5 | $0.00020 | $0.00607 |
| Sonnet 5 | $0.00008 | $0.00243 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
prd-to-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 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD to Plan
$ARGUMENTS
Break a PRD into a phased implementation plan using vertical slices (tracer bullets). Output is a Markdown file in ./plans/.
Usage
/prd-to-plan [PRD issue number or description]
What This Command Does
- Loads the PRD (from GitHub issue or conversation)
- Explores the codebase to understand architecture
- Identifies durable architectural decisions
- Drafts vertical slices (tracer bullets)
- Quizzes user on granularity
- Writes plan file to
./plans/
Process
1. Confirm PRD is in Context
If not provided, ask for the PRD GitHub issue number or content. Fetch with gh issue view <number> if needed.
2. Explore the Codebase
Use Agent (subagent_type=Explore) to understand current architecture, existing patterns, and integration layers.
3. Identify Durable Architectural Decisions
Before slicing, identify decisions unlikely to change:
- Route structures / URL patterns
- Database schema shape
- Key data models
- Authentication / authorization approach
- Third-party service boundaries
4. Draft Vertical Slices
Break PRD into tracer bullet phases. Each phase is a thin vertical slice cutting through ALL layers end-to-end.
| Rule | Description |
|---|---|
| Complete path | Each slice delivers narrow but COMPLETE path through every layer (schema, API, UI, tests) |
| Demoable | A completed slice is demoable or verifiable on its own |
| Thin over thick | Prefer many thin slices over few thick ones |
| Durable | Do NOT include file names, function names, or implementation details likely to change |
| Include decisions | DO include durable decisions: route paths, schema shapes, data model names |
5. Quiz the User
Present breakdown as numbered list. For each phase show:
- Title: short descriptive name
- User stories covered: which stories from the PRD
Ask:
- Does the granularity feel right? (too coarse / too fine)
- Should any phases be merged or split?
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 · 139 lines · 40 tokens per session scan A 90c05f8a71f0
prd-to-plan is a skill published in the GitHub repository softspark/ai-toolkit (172 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 1,214 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
data-governance-guide
Gouvernance des données incluant catalogues, lineage, qualité, ownership, politiques et metadata management. Se déclenche avec "data governance", "gouvernance données", "data catalog", "data lineage", "metadata", "data ownership".
it-commercial-proposal
Génération d'offres commerciales pour des projets IT — lots techniques, chiffrage jour-homme, hypothèses, SLA, TMA et annexes techniques. Se déclenche avec "offre commerciale IT", "proposition commerciale IT", "devis IT", "appel d'offres", "offre technique et financière", "chiffrage jour-homme", "SOW", "réponse à AO".…
developer-onboarding-builder
Création de processus d'onboarding pour nouveaux développeurs. Se déclenche avec "onboarding", "nouveau développeur", "intégration équipe", "setup poste", "getting started guide", "accueil développeur". Also triggers on "onboard a new developer", "developer setup guide", "first week checklist".
orchestrator
Providerneutrales Protokoll zum Zerlegen komplexer Aufgaben, zum Beauftragen unabhängiger Worker und zur evidenzbasierten Abnahme ihrer Ergebnisse.
workflow-extract
Baut aus einem Chatverlauf oder aus bestehenden Automatisierungs-Prompts (z. B. eines anderen Agenten-Systems) eine selbstlaufende, user-neutrale Workflow-Automatisierung: einen wiederkehrenden Prompt bzw. Automations-Skill für Cron/Schedule/Loop. Alias: automations-extractor. Nutze diesen Skill bei „mach daraus eine…
project-onboarding
Standard procedure for onboarding new software projects: Feature analysis, code quality review, onboarding checklist, and task creation.