Borrowing it
Nothing to install: this file belongs to tech-leads-club/nj-mmo. 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/tech-leads-club/nj-mmo/master/.cursor/skills/spec-driven-execution/SKILL.mdgit clone --depth 1 https://github.com/tech-leads-club/nj-mmoWrote 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/tech-leads-club/nj-mmo/spec-driven-execution)<a href="https://agentmods.dev/skills/tech-leads-club/nj-mmo/spec-driven-execution"><img src="https://agentmods.dev/badge/skills/tech-leads-club/nj-mmo/spec-driven-execution/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/tech-leads-club/nj-mmo/spec-driven-execution"><img src="https://agentmods.dev/badge/skills/tech-leads-club/nj-mmo/spec-driven-execution.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.00091 | $0.00813 |
| Opus 5.5 | $0.00036 | $0.00325 |
| Sonnet 5.5 | $0.00018 | $0.00163 |
| Haiku 4.5 | $0.00009 | $0.00081 |
Grade A, and why
spec-driven-execution 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 2mo 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Execution
Driver only. All planning, task format, implementation rules, and validation
live in tlc-spec-driven. This skill does not duplicate them.
What this repo adds
| Delta | Meaning |
|---|---|
| Sub-agent roles | Planner → Implementer → Verifier, each a fresh Composer 2.5 sub-agent (model: composer-2.5). Orchestrator sequences them; never writes spec/code/tests. |
| Single Implementer | One sub-agent runs every task in tasks.md. Skip tlc's per-phase worker offer. |
| Auto-commit in flow | Implementer may commit per task without asking (only while this flow is active). |
| ROADMAP loop | Autonomous mode walks .specs/ROADMAP.md one unchecked phase at a time. |
Orchestrator flow
- Pick phase —
.specs/ROADMAP.md(or loop payload); resume in-flight work from.specs/STATE.md## Handoffif present. - Clean env — free ports 2567 and 4200 before gates.
- Dispatch Planner sub-agent.
- Dispatch Implementer sub-agent (only after Planner artifacts exist under
.specs/features/<feature>/). - Dispatch Verifier sub-agent (always; orchestrator handles fix→re-verify ≤3 iterations per tlc).
- On Verifier PASS — flip ROADMAP
[x], updateSTATE.mdHandoff, commitdocs(spec): mark phase <N> complete in ROADMAP and STATE.
Sub-agent prompts
Sub-agents cannot see this chat. Each prompt is self-contained:
- Activate
tlc-spec-drivenby name and follow it for the assigned role (Specify/Design/Tasks, Execute, or Validate). If the skill cannot be activated, STOP. - Feature context — ROADMAP phase title + goal, feature slug, output dir
.specs/features/<feature>/, repo path/Users/wneto/Dev/nj. - Autonomous mode (loop / unattended) — resolve ambiguities as spec assumptions; no user confirmation gates.
- Project glue (below) — repo inputs tlc does not know about.
- Role footnotes only:
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.
- 2mo ago First seen · 57 lines · 91 tokens per session scan A dff197c98547
spec-driven-execution is a skill published in the GitHub repository tech-leads-club/nj-mmo (36 stars, last pushed 4mo ago), licensed MIT. It adds 91 tokens to every session and 813 once invoked, about $0.0004 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-30.
spec-driven-execution compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| spec-driven-executiontech-leads-club/nj-mmo | Skill | 36 | 4mo ago | MIT | A | 91 | Cursor |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 103 | Claude Code |