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.
git clone --depth 1 https://github.com/hbarbosa02/alaz-mcp-nestjsWrote 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/rules/hbarbosa02/alaz-mcp-nestjs/spec-driven-skill)<a href="https://agentmods.dev/rules/hbarbosa02/alaz-mcp-nestjs/spec-driven-skill"><img src="https://agentmods.dev/badge/rules/hbarbosa02/alaz-mcp-nestjs/spec-driven-skill/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/rules/hbarbosa02/alaz-mcp-nestjs/spec-driven-skill"><img src="https://agentmods.dev/badge/rules/hbarbosa02/alaz-mcp-nestjs/spec-driven-skill.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.00718 | $0.00718 |
| Opus 5 | $0.00359 | $0.00359 |
| Sonnet 5 | $0.00144 | $0.00144 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
spec-driven-skill 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 8d 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven skill — invocation
When to read and follow it
Load .cursor/skills/spec-driven/SKILL.md (and on-demand files under that folder) when the user’s goal matches planning, documenting, or executing work in the adaptive Specify → (Design) → (Tasks) → Execute pipeline, or session / project memory (.specs/). Use natural language; exact phrases are hints, not strict commands.
| Situation | Typical user intent (examples) |
|---|---|
| New / brownfield project | “Initialize project”, “setup project”, “create roadmap”, “map codebase”, “analyze existing code” |
| Feature work | “Specify feature …”, “define requirements”, “design”, “architecture”, “break into tasks”, “implement”, “build”, “validate”, “UAT”, “verify work” |
| Small / ad-hoc | “Quick fix”, “quick task”, “bug fix”, small tweak (use Quick mode when scope is tiny — see below) |
| Continuity | “Pause work”, “end session”, “resume work”, “continue” |
| Project memory | “Record decision”, “log blocker”, “add todo”, “document concerns”, “tech debt” |
Do not treat the spec-driven skill as the right tool for: generic architecture-decomposition analysis (use a dedicated architecture workflow/skill if present), or standalone technical design doc authoring when the user asked for a different doc process (create-technical-design-doc and similar). For everything else in the table, prefer spec-driven.
How to apply it (summary)
- Auto-size depth — Small: Quick mode (describe → implement → verify → commit; guardrails: ~≤3 files, no big design, no new deps). Medium: brief specify + execute with design/tasks inline. Large/complex: full spec IDs,
design.md,tasks.mdas needed. - Phases — Specify and Execute are always in play at the right depth; Design and Tasks are skipped when the change is obvious and small; if inline steps explode (>5 or messy deps), stop and add formal
tasks.md(safety valve). - Artifacts — Put outputs under
.specs/(seeREADME.mdin the skill folder for layout:project/,codebase/,features/,quick/). - Context — Prefer base load:
PROJECT.md,ROADMAP.md,STATE.mdwhen they exist; load one feature’s spec/design/tasks at a time, not several specs in parallel. - Research — Follow the skill’s Knowledge Verification Chain (codebase → project docs → MCP/web → flag uncertainty); do not fabricate APIs or behavior.
- Commits — One logical task or step per commit; commit messages must match this repo’s Conventional Commits rule in
commit-pattern.mdcandnpm run precommitwhen you commit.
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.
- 8d ago First seen · 32 lines · 718 tokens per session scan A c0703cbf021a
spec-driven-skill is a cursor rule published in the GitHub repository hbarbosa02/alaz-mcp-nestjs (2 stars, last pushed 4mo ago), licensed MIT. It adds 718 tokens to every session, about $0.0036 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 cursor rules, from other repositories
rule_main
Core non-negotiable engineering checks.
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
about-codebase
General information about the Lineai MCP Server codebase and its purpose.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.
php-client-implementation
Guidelines for implementing MCP clients in PHP.
cursor_rules
Guidelines for creating and maintaining Cursor rules to ensure consistency and effectiveness.