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 bolivian-peru/os-moda --skill spec-driven-developmentgit clone --depth 1 https://github.com/bolivian-peru/os-modaWrote 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/bolivian-peru/os-moda/spec-driven-development)<a href="https://agentmods.dev/skills/bolivian-peru/os-moda/spec-driven-development"><img src="https://agentmods.dev/badge/skills/bolivian-peru/os-moda/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/bolivian-peru/os-moda/spec-driven-development"><img src="https://agentmods.dev/badge/skills/bolivian-peru/os-moda/spec-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.01802 |
| Opus 5.5 | $0.00022 | $0.00721 |
| Sonnet 5.5 | $0.00011 | $0.00360 |
| Haiku 4.5 | $0.00006 | $0.00180 |
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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Development Skill
You ship software through GitHub's spec-kit (92K stars, MIT, baked into every osModa spawn). The workflow makes you a closed loop: humans declare WHAT and WHY; you generate plan, tasks, code; tests are the inner-loop signal of success; the human is the outer-loop reviewer.
When to invoke spec-kit
Use spec-kit when:
- The user asks for a feature implementation: "build me X", "add Y", "implement Z", "rewrite this so it does W"
- The work spans more than ~5 file edits
- Tests will exist that you can iterate against
- The user wants a reproducible artifact trail (specs, plans, tasks)
Skip spec-kit when:
- One-line fix or typo
- Operational task: use
system-monitor,self-healing,app-deployerinstead - Exploratory hack: free-form chat
- The user explicitly says "just edit the file" / "don't write a spec"
The 8-step workflow
| # | Skill | Purpose |
|---|---|---|
| 1 | speckit-constitution |
Project governance: code style, test policy, language choice |
| 2 | speckit-specify |
What & why (no tech stack yet). User stories with priorities. |
| 3 | speckit-clarify (optional) |
Ask user for gaps before locking the plan |
| 4 | speckit-plan |
Tech stack + architecture choices |
| 5 | speckit-tasks |
Ordered actionable task list |
| 6 | speckit-analyze (optional) |
Cross-artifact consistency check |
| 7 | speckit-checklist (optional) |
Quality gates before implement |
| 8 | speckit-implement |
Generate code, run tests, iterate until green |
How to call from your tool box
The two MCP tools spec_kit_init + spec_kit_run wrap the spec-kit workflow. Use them — don't shell out to specify directly. Tool calls are audit-ledgered; raw shell isn't.
Step 1 — scaffold
spec_kit_init({
project_name: "csv-exporter",
integration: "claude",
constitution_seed: "Python 3.12+, pytest for tests, no async, single binary"
})
Returns { project_path: "/workspace/csv-exporter", skills: [9 speckit-*], next_action }. The 9 skills become available as /speckit-* slash commands inside that project.
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 · 171 lines · 56 tokens per session scan A 31244b0cebf4
spec-driven-development is a skill published in the GitHub repository bolivian-peru/os-moda (120 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,802 once invoked, about $0.0002 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-30.
Other skills, from other repositories
cicd-pipeline-qe-orchestrator
Orchestrate quality engineering across CI/CD pipeline phases. Use when designing test strategies, planning quality gates, or implementing shift-left/shift-right testing.
implement__feature
A three-phase workflow for carrying out implementation tasks. It plans and tests the work, delegates implementation using test-driven development (TDD), then runs repeated code reviews.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.