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 kambleakash0/agent-skills --skill spec-to-plangit clone --depth 1 https://github.com/kambleakash0/agent-skillsWrote 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/kambleakash0/agent-skills/spec-to-plan)<a href="https://agentmods.dev/skills/kambleakash0/agent-skills/spec-to-plan"><img src="https://agentmods.dev/badge/skills/kambleakash0/agent-skills/spec-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/kambleakash0/agent-skills/spec-to-plan"><img src="https://agentmods.dev/badge/skills/kambleakash0/agent-skills/spec-to-plan.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.01246 |
| Opus 5 | $0.00010 | $0.00623 |
| Sonnet 5 | $0.00004 | $0.00249 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
spec-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 11d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Turn a PRD into an Implementation Plan
This skill translates what needs to be built (the PRD) into how it will be built (a phased implementation plan). It breaks the PRD into tracer-bullet vertical slices, orders them into phases, and writes the result as a Markdown plan file in ./plans/.
When to Use
Use this skill when:
- You already have a PRD or equivalent spec and now need a concrete implementation plan.
- You want to think in phases, not just issues: what gets built first, what can be deferred, and how slices build on each other.
- You intend to drive downstream work (e.g.
/slice-the-spec,/incremental-tdd) from a single, durable planning document.
If the requirements are still fuzzy, use /grill-me and /spec-writer first.
Workflow
You can compress steps if the context is already clear, but keep the core structure: PRD → slices → phases → plan file.
-
Confirm the PRD is in context
- Ensure the PRD is available in the conversation or repo.
- If not, ask the user to paste it or point you to the file path or issue.
- Skim for: goals, user stories, functional requirements, non-goals, and constraints.
-
Explore the codebase (light)
- If you have not already explored the codebase for this feature, do a quick pass to understand major modules, integration layers, and architectural patterns.
- Note any constraints that will affect slicing (e.g. existing routing, data models, auth, third-party boundaries).
-
Identify durable architectural decisions
Before slicing, identify decisions that are unlikely to change across phases and are worth calling out up front:
- Route structures / URL patterns.
- Database schema shape and key tables.
- Core data models and domain concepts.
- Authentication / authorization approach.
- Third‑party service boundaries and integration points.
These go into the Architectural decisions section of the plan so every phase can reference them.
-
Draft vertical slices (tracer bullets)
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.
- 11d ago First seen · 148 lines · 21 tokens per session scan A 0946f517fc8a
spec-to-plan is a skill published in the GitHub repository kambleakash0/agent-skills (9 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 1,246 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
weather
Get current weather and forecasts (no API key required).
canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
dashboard-builder
Build self-contained interactive HTML dashboards with charts, filters, and tables. Generates a single browser-openable file — no server or dependencies required.
bionic-decision-engine
Unified mathematical arbitrator for all resource allocation decisions — money, time, energy, relationships. Absorbs 46 decision protocols + 24 strategy protocols into one dense engine.
gemigo-cli
Use when the user wants to publish an already-built static website or front-end app through GemiGo, such as a Vite/React/Vue static build, plain HTML/CSS/JS page, landing page, demo, docs site, or small browser app, and get a hosted public URL.
clawhub-nextclaw
Use when the user wants to search external ClawHub skills or install a ClawHub skill into a NextClaw workspace's skills directory without treating ClawHub as the NextClaw marketplace.