What is implement-spec?

A disciplined workflow for implementing one written specification exactly as provided. It treats the specification and its tests as the authority and stops if the requested changes conflict with the repository.

Use it when a specification file lists a feature to build, its files to change, constraints, and required tests; the workflow checks the clean baseline, repository maps, file status, and implementation result.

It limits design guesswork and makes conflicts visible before code is changed, which is useful when another person or process has already made the technical decisions.

implement-spec — Skill for Claude Code and Codex by kunalsuri: A disciplined workflow for implementing one written specification exactly…

Install

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.

agentmods

npx agentmods add skills/kunalsuri/ai-fication-kit/implement-spec

Any agent

npx skills add kunalsuri/ai-fication-kit --skill implement-spec

Clone the repo

git clone --depth 1 https://github.com/kunalsuri/ai-fication-kit

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/kunalsuri/ai-fication-kit/implement-spec.svg)](https://agentmods.dev/skills/kunalsuri/ai-fication-kit/implement-spec)

Your own site

<a href="https://agentmods.dev/skills/kunalsuri/ai-fication-kit/implement-spec"><img src="https://agentmods.dev/badge/skills/kunalsuri/ai-fication-kit/implement-spec.svg" alt="Measured on agentmods" height="20"></a>

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,159 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00046	$0.01159
Opus 5	$0.00023	$0.00580
Sonnet 5	$0.00009	$0.00232
Haiku 4.5	$0.00005	$0.00116

Measured 4d ago against content hash 7c1267c645f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

implement-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 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.

.claude/skills/implement-spec/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement the spec at: $ARGUMENTS (If no path was given, ask for one and stop. Implement ONLY this spec.)

You are the implementer, not the designer. Every design decision has already been made in the spec. Your job is faithful translation into code, and loud, early reporting when translation is impossible.

Protocol (follow in order, no skipping)

0. Load context — exactly this, no more

Read the ENTIRE spec file, top to bottom, before writing any code.
Read any rationale/lessons-learnt doc the spec's preamble names — once.
Read ai/guide/MODULE_MAP.md (Stability column) and ai/guide/CONVENTIONS.md.
Do NOT crawl the tree. Open other files only when the spec's touch list or your current step requires them.

1. Pre-flight (all must pass before you write code)

npm test passes on the clean checkout (record the pass count).
node install.mjs verify . --strict passes.
Every file in the spec's touch list marked "modify" exists; confirm none is frozen or ? in MODULE_MAP.md. If one is → STOP AND REPORT.
Restate to yourself the spec's hard-constraints table (if present). Those constraints outrank your habits and your training priors.

2. THE PRIME RULE — stop-and-report, never improvise

If at ANY point the spec conflicts with what you find in the code, the docs, or a failing behaviour — the function signature differs, a file isn't where the spec says, an example contradicts a rule, a specified test cannot pass as written — you MUST stop and report:

the spec section, the file:line evidence, and the smallest question whose answer unblocks you. Do NOT pick the "obvious" interpretation. Do NOT patch around it. Do NOT widen scope to fix it. A wrong guess here costs more than the pause. This rule exists because specs are [inferred] artifacts: mostly right, wrong in confident-sounding places.

3. Implement

Follow the spec's own ordering and any code skeleton it provides — structure, export names, and file layout are contractual, not suggestions.
Touch ONLY files in the spec's touch list. No new dependencies unless the spec adds them. No drive-by refactors, renames, or "improvements".
License header on every new file, copied from a neighbouring file.
Match surrounding code style (imports, naming, error handling) over generic best practice.

Read the full file on GitHub · 88 lines

Changes

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 · 88 lines · 46 tokens per session scan A 7c1267c645f7

Subscribe to this mod's changes

implement-spec is a skill published in the GitHub repository kunalsuri/ai-fication-kit (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 1,159 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-31.

Planning Productivity Testing Web3 and blockchain agent-skills ai antigravity context-engineering software-engineering

mantis-threat-model

Synthesizes trust boundaries, attack surfaces, and attacker profiles into a living threat model. Use as Stage B of the Knowledge Base generation process, reading architecture and entity definitions from the KB. Don't use for analyzing source code or extracting raw learnings from JSONL files.

google/mantis · 59 tokens

blockchain-developer

Build production-ready Web3 applications, smart contracts, and decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations. Use PROACTIVELY for smart contracts, Web3 apps, DeFi protocols, or blockchain infrastructure.

rmyndharis/antigravity-skills · 56 tokens

implement-spec