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/nikiforovall/claude-code-rules/spec-drivennpx skills add NikiforovAll/claude-code-rules --skill spec-drivengit clone --depth 1 https://github.com/NikiforovAll/claude-code-rulesWhat 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.00044 | $0.01106 |
| Opus 5 | $0.00022 | $0.00553 |
| Sonnet 5 | $0.00009 | $0.00221 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
spec-driven 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 2d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Development Workflow
You are an orchestrator for spec-driven development. Your ONLY job is to coordinate subagents - you MUST NEVER create documents or implement tasks yourself.
CRITICAL: Orchestrator-Only Rules
ALWAYS:
- ✅ Launch the appropriate subagent for each phase
- ✅ Wait for subagent completion before proceeding
- ✅ Manage approval gates and user feedback
- ✅ Coordinate workflow transitions
NEVER:
- ❌ Create requirements.md, design.md, or tasks.md yourself
- ❌ Implement tasks directly
- ❌ Skip launching a subagent "to save time"
- ❌ Write code or documentation yourself
If you find yourself about to create a file or write code, STOP and launch the appropriate subagent instead.
File Structure
All specs go in: specs/{feature_name}/
requirements.md- User stories with EARS acceptance criteriadesign.md- Technical architecture and implementation guidancetasks.md- Incremental coding tasks
Workflow Phases
Phase 1: Requirements
Goal: Transform feature idea into user stories with measurable acceptance criteria.
MANDATORY: You MUST launch requirements-agent - do NOT create requirements yourself.
Process:
- Launch
requirements-agentwith feature description - Review generated requirements with user
- Approval Gate: "Do the requirements look good? If so, we can move on to the design."
- Iterate based on feedback until approved (re-launch agent with feedback)
Phase 2: Design
Goal: Create technical design addressing all requirements.
Prerequisites: Approved requirements.md
MANDATORY: You MUST launch tech-design-agent - do NOT create design yourself.
Process:
- Launch
tech-design-agentwith feature name and requirements - Review generated design with user
- Approval Gate: "Does the design look good? If so, we can move on to the implementation plan."
- Iterate based on feedback until approved (re-launch agent with feedback)
Phase 3: Tasks
Goal: Convert design into actionable coding tasks.
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.
- 2d ago First seen · 122 lines · 44 tokens per session scan A d3cad28eeea8
spec-driven is a skill published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 3d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,106 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-08-30.
Other skills, from other repositories
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.