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 H2Sxxa/spec-coding-skills --skill spec-plangit clone --depth 1 https://github.com/H2Sxxa/spec-coding-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/h2sxxa/spec-coding-skills/spec-plan)<a href="https://agentmods.dev/skills/h2sxxa/spec-coding-skills/spec-plan"><img src="https://agentmods.dev/badge/skills/h2sxxa/spec-coding-skills/spec-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.1 | $0.00078 | $0.01909 |
| Opus 5 | $0.00039 | $0.00955 |
| Sonnet 5 | $0.00016 | $0.00382 |
| Haiku 4.5 | $0.00008 | $0.00191 |
Grade A, and why
spec-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 6d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Planning
Use this skill when the task is still fuzzy and the agent should define success before implementation begins.
This skill turns a request into a practical spec. The goal is not project-management theater. The goal is to make coding safer and faster by clarifying scope, constraints, edge cases, validation, and what counts as done.
Bundled resources
references/self-check.mddefines the self-check checklist, ambiguity handling, blocking-question rules, execution guardrails, and change-control policy.references/output-template.mddefines the preferred implementation-ready spec output shape for persisted task specs and complex conversation plans.
Read references/self-check.md before finalizing a persisted task spec, handing a plan to implementation, or when ambiguity could lead to execution-time guessing.
Use references/output-template.md when writing a persisted task spec or a complex plan that needs stable structure.
Repository preference override
Before doing anything else, look for a SPEC.md in the target repository root.
If it exists, treat it as the repository-specific preference layer for:
- shared validation rules
- environment and configuration constraints that affect planning
- knowledge-base location
- cross-skill workflow conventions
If it is missing, use the built-in defaults for this skill series instead of blocking on the missing file.
If it is partial, use the fields it defines and fall back to defaults for the rest.
Built-in defaults
When no repository root SPEC.md is available, use these defaults:
- validation behavior: prefer discoverable repository tooling; if no validation commands are discoverable, say validation is not configured yet
- knowledge-base location:
docs/knowledge-base/ - task spec location:
docs/specs/<slug>.md - task execution mode: keep the plan in conversation for small, well-bounded tasks; persist it for complex, risky, or multi-turn work
- context retrieval: query
spec-indexfor relevant decisions, constraints, setup notes, pitfalls, and validation rules before planning non-trivial work - self-check: apply
references/self-check.mdbefore implementation handoff
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 192 lines · 78 tokens per session scan A 1a4cd568be96
spec-plan is a skill published in the GitHub repository H2Sxxa/spec-coding-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 1,909 once invoked, about $0.0004 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
Execute BDD scenarios
Execute BDD test scenarios from .feature files using browser automation.
Draft a story markdown from a story tracker or feature description
Generate a draft story markdown by analyzing a story tracker or feature description, Figma designs, and the codebase.
Learn why to review implementation even with 100% test coverage
Interactive guidance on why human code review is essential for readability and maintainability.
Learn what defines effective BDD scenarios
Interactive guidance on writing complete, effective BDD scenarios for story-flow.
Learn why to discuss technical design before implementation
Interactive guidance on creating technical design PRs to align with your team before coding.
Analyze task dependencies for parallel execution
Parse story markdown to identify task dependencies and parallel execution opportunities.