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 skills add kunalsuri/ai-fication-kit --skill implement-specgit clone --depth 1 https://github.com/kunalsuri/ai-fication-kitWrote 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/kunalsuri/ai-fication-kit/implement-spec)<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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.00046 | $0.01159 |
| Opus 5.5 | $0.00018 | $0.00464 |
| Sonnet 5.5 | $0.00009 | $0.00232 |
| Haiku 4.5 | $0.00005 | $0.00116 |
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 1mo 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.
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) andai/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 testpasses on the clean checkout (record the pass count).node install.mjs verify . --strictpasses.- Every file in the spec's touch list marked "modify" exists; confirm none is
frozenor?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.
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.
- 1mo ago First seen · 88 lines · 46 tokens per session scan A 7c1267c645f7
implement-spec is a skill published in the GitHub repository kunalsuri/ai-fication-kit (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,159 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
mantis-configure
Configures and validates Mantis pipeline environments, sandbox mechanisms, and AI models. Use to set up workflow.json, auto-detect host capabilities, switch between sandboxes (static-only, gvisor, microsandbox, gce), select AI models, and run fast 1-2s preflight tests. Don't use for scanning source code or running…
prompt-proximity-architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited…
09-for-sure
Run an iterative agent loop that retries until a runnable success condition passes. Use when the user says "for sure", "keep trying until", or wants guaranteed completion against a success command. Not for one-shot tasks or uncheckable goals.
verify
Run x-harness read-only verification.
execute
Implements a plan step by step, verifies named tests or explicit manual scenarios, enforces the product-behavior guardrail and five-attempt retry limit, and completes with the plan's automated regression gate or validated manual evidence. Use when executing a plan that plan-the-work already wrote.
define-test-strategy
Onboards or refreshes a repo's test-strategy skill and shared test map: discovers tests across repos without modifying source/tests, discusses layers and adoption, records commands and prerequisites, maintains evidence-backed UC/domain relationships, and reports coverage.