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/w00fx/spec-anchored-agentic-development/implementgit clone --depth 1 https://github.com/w00fx/spec-anchored-agentic-developmentWhat 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.00013 | $0.00132 |
| Opus 5 | $0.00006 | $0.00066 |
| Sonnet 5 | $0.00003 | $0.00026 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
implement 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 2d 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.
What it actually says
/implement — redirect
The transactional skills are user-invocation-only — a command body cannot load them for you. Reply to the user with exactly this and do nothing else:
Invoke the mode adapter directly:
/implement-feature <issue | spec slice | task>for supervised local work. Orchestrated workers use/implement-orchestrated; unattended loops use/implement-backlog(launcher-invoked). This wrapper exists only to point you there.
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.
- 2d ago First seen · 16 lines · 13 tokens per session scan A 2886ace20f9d
implement is a command published in the GitHub repository w00fx/spec-anchored-agentic-development (5 stars, last pushed 7d ago), licensed MIT. It adds 13 tokens to every session and 132 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-31.
Other commands, from other repositories
spec-kitty-standalone
This host should read Spec Kitty's canonical standalone-invocation skill pack at.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
research
Gather external knowledge into §R so build grounds in facts, not hallucinations. Every finding cites a source.
validate-design
Interactive technical design quality review and validation.
sync-linear
Sync current work with Linear ticket status.
kiro-validate-design
Command "kiro-validate-design" from gotalab/cc-sdd, covering technical design validation, core task, execution steps, important constraints and tool guidance.