agentmods.dev

nj-mmo: Skill for Cursor

.cursor/skills/spec-driven-execution/SKILL.md

spec-driven-execution is a skill for Cursor from tech-leads-club/nj-mmo. It costs 91 tokens per session (813 once invoked), scanned A, original, MIT.

An orchestration procedure for building the next planned feature in an MMO repository. It sends separate planning, implementation, and verification tasks to fresh subagents and follows the project roadmap.

In plain words
What is it for?
Use it to advance a roadmap phase, coordinate the Planner, Implementer, and Verifier roles, and complete the required checks for a feature.
Why use it?
It keeps feature work structured and makes verification an explicit stage. The workflow also supports resuming unfinished work and limited fix-and-recheck cycles.

Skill for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions subagents; mentions AGENTS.md.

This is tech-leads-club/nj-mmo's own configuration. It tells Cursor how to work on nj-mmo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything nj-mmo configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/wneto/Dev/nj.

not rated 23repo +2 2mo ago A scan 91 tokens original MIT
View source ↗ tech-leads-club/nj-mmo
Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/tech-leads-club/nj-mmo/master/.cursor/skills/spec-driven-execution/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/tech-leads-club/nj-mmo

Made for: Cursor.

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.

agentmods badge for spec-driven-execution

README.md
[![agentmods](https://agentmods.dev/badge/skills/tech-leads-club/nj-mmo/spec-driven-execution/github.svg)](https://agentmods.dev/skills/tech-leads-club/nj-mmo/spec-driven-execution)
Your own site
<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.

agentmods 80×15 button for spec-driven-execution

Your own site · 80×15
<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>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 813 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00091 $0.00813
Opus 5 $0.00046 $0.00407
Sonnet 5 $0.00018 $0.00163
Haiku 4.5 $0.00009 $0.00081

Measured 10d ago against content hash dff197c98547, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 10d 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.

.cursor/skills/spec-driven-execution/SKILL.md · 57 lines

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

  1. Pick phase — .specs/ROADMAP.md (or loop payload); resume in-flight work from .specs/STATE.md ## Handoff if present.
  2. Clean env — free ports 2567 and 4200 before gates.
  3. Dispatch Planner sub-agent.
  4. Dispatch Implementer sub-agent (only after Planner artifacts exist under .specs/features/<feature>/).
  5. Dispatch Verifier sub-agent (always; orchestrator handles fix→re-verify ≤3 iterations per tlc).
  6. On Verifier PASS — flip ROADMAP [x], update STATE.md Handoff, commit docs(spec): mark phase <N> complete in ROADMAP and STATE.

Sub-agent prompts

Sub-agents cannot see this chat. Each prompt is self-contained:

  1. Activate tlc-spec-driven by name and follow it for the assigned role (Specify/Design/Tasks, Execute, or Validate). If the skill cannot be activated, STOP.
  2. Feature context — ROADMAP phase title + goal, feature slug, output dir .specs/features/<feature>/, repo path /Users/wneto/Dev/nj.
  3. Autonomous mode (loop / unattended) — resolve ambiguities as spec assumptions; no user confirmation gates.
  4. Project glue (below) — repo inputs tlc does not know about.
  5. Role footnotes only:

Read the full file on GitHub · 57 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.

  1. 10d ago First seen · 57 lines · 91 tokens per session scan A dff197c98547

Subscribe to this mod's changes

spec-driven-execution is a skill published in the GitHub repository tech-leads-club/nj-mmo (23 stars, last pushed 2mo ago), licensed MIT. It adds 91 tokens to every session and 813 once invoked, about $0.0005 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-30.

Building agentsPlanning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens