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 hamza-ali-shahjahan/hamzaish --skill spec-driven-developmentgit clone --depth 1 https://github.com/hamza-ali-shahjahan/hamzaishWrote 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/hamza-ali-shahjahan/hamzaish/spec-driven-development)<a href="https://agentmods.dev/skills/hamza-ali-shahjahan/hamzaish/spec-driven-development"><img src="https://agentmods.dev/badge/skills/hamza-ali-shahjahan/hamzaish/spec-driven-development/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/hamza-ali-shahjahan/hamzaish/spec-driven-development"><img src="https://agentmods.dev/badge/skills/hamza-ali-shahjahan/hamzaish/spec-driven-development.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.00043 | $0.01892 |
| Opus 5.5 | $0.00017 | $0.00757 |
| Sonnet 5.5 | $0.00009 | $0.00378 |
| Haiku 4.5 | $0.00004 | $0.00189 |
Grade A, and why
spec-driven-development 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 1mo 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.
This is a copy
100% identical to spec-driven-development — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Development
Overview
Write a structured specification before writing any code. The spec is the shared source of truth between you and the human engineer — it defines what we're building, why, and how we'll know it's done. Code without a spec is guessing.
When to Use
- Starting a new project or feature
- Requirements are ambiguous or incomplete
- The change touches multiple files or modules
- You're about to make an architectural decision
- The task would take more than 30 minutes to implement
When NOT to use: Single-line fixes, typo corrections, or changes where requirements are unambiguous and self-contained.
The Gated Workflow
Spec-driven development has four phases. Do not advance to the next phase until the current one is validated.
SPECIFY ──→ PLAN ──→ TASKS ──→ IMPLEMENT
│ │ │ │
▼ ▼ ▼ ▼
Human Human Human Human
reviews reviews reviews reviews
Phase 1: Specify
Start with a high-level vision. Ask the human clarifying questions until requirements are concrete.
Surface assumptions immediately. Before writing any spec content, list what you're assuming:
ASSUMPTIONS I'M MAKING:
1. This is a web application (not native mobile)
2. Authentication uses session-based cookies (not JWT)
3. The database is PostgreSQL (based on existing Prisma schema)
4. We're targeting modern browsers only (no IE11)
→ Correct me now or I'll proceed with these.
Don't silently fill in ambiguous requirements. The spec's entire purpose is to surface misunderstandings before code gets written — assumptions are the most dangerous form of misunderstanding.
Write a spec document covering these six core areas:
-
Objective — What are we building and why? Who is the user? What does success look like?
-
Commands — Full executable commands with flags, not just tool names.
Build: npm run build Test: npm test -- --coverage Lint: npm run lint --fix Dev: npm run dev
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.
- 1mo ago First seen · 217 lines · 43 tokens per session scan A 505939e15bf6
spec-driven-development is a skill published in the GitHub repository hamza-ali-shahjahan/hamzaish (11 stars, last pushed 18d ago), licensed MIT. It adds 43 tokens to every session and 1,892 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to spec-driven-development, differing in 16 lines, and is treated as a copy.
Other skills, from other repositories
gingiris-launch
A multilingual launch guide for releasing an AI product on Product Hunt and other marketing channels. Product Hunt is a website where new technology products are presented to an audience and ranked through community attention.
payments-polar
A reference for adding Polar payments to a product, covering Polar as the seller of record, payment types, checkout, webhooks, and customer access.
stack-reference
A setup guide for the AI Garage technology stack, covering tools for code hosting, web apps, databases, user accounts, analytics, email, and payments.
unit-economics
A guide to measuring how people discover, use, and pay for a product. It explains metrics such as CAC, LTV, retention, cohorts, and UTM tracking.
traffic-channels
A reference guide to 12 traffic channels, such as search engines, social networks, advertising, and developer communities. It compares who each channel reaches, how quickly it can work, and the usual time or budget involved.
make-playbook
An indie maker playbook inspired by Pieter Levels' (@levelsio) book "MAKE: The Indie Maker Blueprint" — idea validation, fast/DIY building, launching, organic growth, monetization, automation, and exits for bootstrapped apps. Use when the user is starting a new app idea, deciding what to build or build next, prepping…