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 phuonghx/aim-cli --skill spec-driven-developmentgit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/phuonghx/aim-cli/spec-driven-development)<a href="https://agentmods.dev/skills/phuonghx/aim-cli/spec-driven-development"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/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/phuonghx/aim-cli/spec-driven-development"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/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.00098 | $0.01289 |
| Opus 5.5 | $0.00039 | $0.00516 |
| Sonnet 5.5 | $0.00020 | $0.00258 |
| Haiku 4.5 | $0.00010 | $0.00129 |
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.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Development
Agree on what and how before writing a single line of code.
Inspired by GitHub spec-kit and AWS Kiro: capture intent in three living documents, gate each on approval, and let the spec — not memory — be the source of truth the agent codes against.
When to write a spec (vs. skip it)
| Write a spec | Skip it |
|---|---|
| New feature or capability | One-line / typo fix |
| Touches 3+ files or modules | Single obvious change |
| Requirements are fuzzy or contested | Behavior is fully clear |
| Cross-cutting (auth, data model, API) | Local refactor with tests already green |
| You'd struggle to write a test for it | You can already name the assertion |
Rule of thumb: if you can't state the acceptance test in one sentence, you need a spec.
The three artifacts
Each is one file. Keep them short and current; stale specs are worse than none.
requirements.md— WHAT & WHY. Problem statement, user stories (As a <role>, I want <capability>, so that <benefit>), and numbered requirements R1, R2… Each requirement carries EARS acceptance criteria (see theears-acceptance-criteriaskill). No solution detail here.design.md— HOW. Architecture, components, data model, and the trade-offs / alternatives considered. Reference requirements by id (R1, R2) so coverage is traceable. Name the risks and open questions.tasks.md— STEPS. Dependency-ordered, checkable task list derived from the design. Mark independent items[P](parallel). Every task should map back to a requirement and be independently verifiable.
The left-to-right approval gate
requirements.md ──approve──▶ design.md ──approve──▶ tasks.md ──approve──▶ CODE
WHAT HOW STEPS implement
- Do not move right until the current artifact is approved. No design before requirements are agreed; no code before design is approved.
- New information flows left: a discovery while coding updates
tasks.md, and if it changes intent, bumpdesign.md/requirements.mdand re-confirm. - The gate is a checkpoint, not a contract — keep each pass lightweight.
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 · 119 lines · 98 tokens per session scan A abcd98b6a646
spec-driven-development is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 3mo ago), licensed MIT. It adds 98 tokens to every session and 1,289 once invoked, about $0.0004 per session on Opus 5.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
memory-retain
Save what was learned to Hindsight long-term memory. Use when a task finishes, when the user states a fact, decision or preference, and when you discover something a later run or another Bot would need.
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
web-platform-baseline
Use this skill before asserting that a CSS, HTML or accessibility capability is available, unavailable, or the right tool — it carries dated, refreshable platform facts and refuses to let stale knowledge be stated as current. Triggers: user says "container query", "can I use", "browser support", "modern CSS", ":has"…
doc-coauthoring
Collaboratively author technical specifications, RFCs, PRDs, ADRs, and decision documents through structured context gathering, iterative refinement, and blind reader testing. Use when drafting substantial documentation, architecture proposals, or engineering design records.