Borrowing it
Nothing to install: this file belongs to w00fx/spec-anchored-agentic-development. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/w00fx/spec-anchored-agentic-development/main/.agents/skills/implement/SKILL.mdgit clone --depth 1 https://github.com/w00fx/spec-anchored-agentic-developmentWrote 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/w00fx/spec-anchored-agentic-development/implement)<a href="https://agentmods.dev/skills/w00fx/spec-anchored-agentic-development/implement"><img src="https://agentmods.dev/badge/skills/w00fx/spec-anchored-agentic-development/implement.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.1 | $0.00015 | $0.00111 |
| Opus 5 | $0.00008 | $0.00056 |
| Sonnet 5 | $0.00003 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
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 — supervised alias
This skill is an explicit user-invoked alias for the supervised Owner workflow.
Read and follow .agents/skills/implement-feature/SKILL.md in full, using the
current argument as its task input. Do not select an orchestrated or unattended
mode unless the user explicitly invoked that mode instead.
What ships with it
1 file 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.
- 2d ago First seen · 13 lines · 15 tokens per session scan A eeeea48ad0a3
implement is a skill published in the GitHub repository w00fx/spec-anchored-agentic-development (5 stars, last pushed 4d ago), licensed MIT. It adds 15 tokens to every session and 111 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-09-05.
Other skills, from other repositories
Accept
The boundary ritual — review what just landed, record an approval, journal it, and advance the phase. The ONLY step that writes approvals, and it does NO git.
A5 — Web Audit
Research the world. Real web research to find what the best teams do for every technology and pattern in the build, then implement superior approaches now (not later). The only lens that brings outside knowledge.
Brainstorm
Interactive ideation and decision capture at any pipeline boundary. Opinionated dialogue that surfaces contradictions, gaps, and untested assumptions — not template-filling. Feeds the Furnace.
Init
Initialize Genesis Spec-Kit in a project — scaffold .genesis/ and determine the project mode (greenfield, brownfield, lowfield). Use when setting up the kit for the first time.
Specify
Write the master spec — the WHAT. User stories, functional & non-functional requirements, acceptance criteria, and the dependency-ordered micro-spec plan. Strictly WHAT, never HOW.
A1 — Design & Master-Spec Consistency
The drift check. Compare what was built against the design doc and master spec. Sets the Double Gate — A3 cannot start until A1 is at zero findings.