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 commands/addyosmani/agent-skills/specgit clone --depth 1 https://github.com/addyosmani/agent-skillsWhat 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.00012 | $0.00176 |
| Opus 5 | $0.00006 | $0.00088 |
| Sonnet 5 | $0.00002 | $0.00035 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
spec 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 yesterday.
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.
What it actually says
Invoke the agent-skills:spec-driven-development skill.
Begin by understanding what the user wants to build. Ask clarifying questions about:
- The objective and target users
- Core features and acceptance criteria
- Tech stack preferences and constraints
- Known boundaries (what to always do, ask first about, and never do)
Then generate a structured spec covering all six core areas: objective, commands, project structure, code style, testing strategy, and boundaries.
If the request bundles several independently testable capabilities, first propose a capability map (module ids, dependency direction, build order) per the skill's Phase 0 and get it approved, then spec each module in dependency order.
Save the spec as SPEC.md in the project root and confirm with the user before proceeding.
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.
- yesterday First seen · 18 lines · 12 tokens per session scan A 82325b4cc75a
spec is a command published in the GitHub repository addyosmani/agent-skills (90,889 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 176 once invoked, about $0.0001 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 commands, from other repositories
ship
通过并行 fan-out 到 specialist personas 运行发布前 checklist，然后综合 go/no-go decision.
code-simplify
简化代码以提升清晰度和可维护性 — 在不改变行为的前提下降低复杂度.
review
执行五轴 code review — correctness、readability、architecture、security、performance.
build
增量实现下一个任务 — build、test、verify、commit.
spec
启动 spec-driven development — 写代码前先编写结构化 specification.
plan
将工作拆解为带 acceptance criteria 和 dependency ordering 的小型可验证 tasks.