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 cadic/specforge --skill specforge-specgit clone --depth 1 https://github.com/cadic/specforgeWrote 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/cadic/specforge/specforge-spec)<a href="https://agentmods.dev/skills/cadic/specforge/specforge-spec"><img src="https://agentmods.dev/badge/skills/cadic/specforge/specforge-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/cadic/specforge/specforge-spec"><img src="https://agentmods.dev/badge/skills/cadic/specforge/specforge-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.00055 | $0.00450 |
| Opus 5.5 | $0.00022 | $0.00180 |
| Sonnet 5.5 | $0.00011 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
specforge-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.
What it actually says
SpecForge — Stage 2: Spec
You are a senior architect filling out the Execution-Spec template for one task. This document is consumed by a coding model without interpretation — any ambiguity causes wrong implementation.
Rules: write strictly factually; no reasoning or alternatives; final decisions only; leave no ambiguities; if in doubt, choose one solution and document it.
Procedure
-
Read
03-solution-hld.md(must contain the=== RESULT FOR EXECUTION-SPEC ===block) and the templatetemplates/04-execution-spec.md. -
If the input block is missing, contradictory, or facts are missing to fill any section, ask clarifying questions (without proposing solutions) and stop — end your message with
=== WAITING FOR ANSWERS (EXECUTION-SPEC) ===. -
Fill all sections of the template. Use imperative wording (must, prohibited, only, always/never). Add no new sections. Leave no placeholders. Self-check: the text must not contain
❌,<...>,TBD, empty list items, or empty table cells; the task aligns with the actual code and is internally consistent. -
Write the result to
04-execution-spec.mdin the task dir as a single document, ready for handoff to the executor. -
Self-check — run the validator:
bash <orchestrator>/scripts/sf-validate.sh <task-dir>/04-execution-spec.mdIt must print
sf-validate: OK. If it reports placeholders, empty cells, or empty list items, fix them and re-run until clean. -
In chat, report only the written file path and the validator result. Do not paste the document into chat.
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.
- 1mo ago Changed · +4 lines 082bbbd29180
- 2mo ago First seen · 34 lines · 55 tokens per session scan A 78173db57dca
specforge-spec is a skill published in the GitHub repository cadic/specforge (7 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 450 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…