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/bish-x/bx-dev-skill/spec-driven-workflownpx skills add bish-x/bx-dev-skill --skill spec-driven-workflowgit clone --depth 1 https://github.com/bish-x/bx-dev-skillWrote 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/bish-x/bx-dev-skill/spec-driven-workflow)<a href="https://agentmods.dev/skills/bish-x/bx-dev-skill/spec-driven-workflow"><img src="https://agentmods.dev/badge/skills/bish-x/bx-dev-skill/spec-driven-workflow.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 | $0.00037 | $0.03502 |
| Opus 5 | $0.00018 | $0.01751 |
| Sonnet 5 | $0.00007 | $0.00700 |
| Haiku 4.5 | $0.00004 | $0.00350 |
Grade A, and why
spec-driven-workflow 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
3 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.
- 4d ago First seen · 334 lines · 37 tokens per session scan A f4eab8a81a5b
spec-driven-workflow is a skill published in the GitHub repository bish-x/bx-dev-skill (23 stars, last pushed 3mo ago), with no licence file. It adds 37 tokens to every session and 3,502 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
speckit.specify
Feature Definer - Generates spec.md from natural language description.
game-performance-budget
Use when defining or reviewing game frame-time, memory, loading, network, CPU, GPU, allocation, or thermal budgets against captured measurements and target hardware tiers.
studio-workspace-routing
Use when .agents/project-profile.yaml, nested Git roots, or cross-repository game work requires a profile-defined repository route, validation slice, or cross-project phase.
speckit.uiux
UI/UX Architect - Definition of Design System Anti-Slop, UI Components, Spacing, Typography, Responsive Patterns.
speckit.architecture
Software Architect - Make evidence-based system design decisions, document trade-offs and ADRs, and define modular, reliable implementation boundaries.
api-error-taxonomy
Define consistent API error codes and responses. Use when a mid-level developer needs error standardization.