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 skills/cadic/specforge/specforge-executenpx skills add cadic/specforge --skill specforge-executegit clone --depth 1 https://github.com/cadic/specforgeWhat 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.00068 | $0.00420 |
| Opus 5 | $0.00034 | $0.00210 |
| Sonnet 5 | $0.00014 | $0.00084 |
| Haiku 4.5 | $0.00007 | $0.00042 |
Grade A, and why
specforge-execute 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
SpecForge — Stage 3: Execute
Implement the task strictly from 04-execution-spec.md. This stage runs on a
coding model.
Executor discipline (methodology-level — always applies)
- The Execution-Spec is the single source of truth.
- If a requirement is not in the spec, it does not exist — do not add undocumented behavior, improvements, or optimizations "at your discretion".
- Do not rethink the architecture or deviate from the spec.
- On any ambiguity or contradiction — ask a question, do not guess.
- Section 11 (Decision Rationale) is read-only: never use it to justify a change.
- For code style, naming, security, and testing conventions, follow the
project's own
AGENTS.md/CLAUDE.md. SpecForge does not own that file.
Procedure
- Read
04-execution-spec.mdend to end before writing any code. - Read the project's
AGENTS.md/CLAUDE.md(if present) for code standards. - Implement sections 3, 4, 5, 6, and 8 exactly as written.
- Respect section 7 (Out of Scope) and section 8.2 (What Not To Do).
- Write the tests described in section 9.
- Before claiming completion, run the Definition-of-Done self-verify in
references/checklist.md.
If the spec is internally contradictory or missing facts you need, stop and ask the user — return to Stage 2 if the spec itself must change.
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 · 35 lines · 68 tokens per session scan A 35318890cb67
specforge-execute is a skill published in the GitHub repository cadic/specforge (5 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 420 once invoked, about $0.0003 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 skills, from other repositories
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…