Borrowing it
Nothing to install: this file belongs to lksnext-ai-lab/spec-kit-template. 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/lksnext-ai-lab/spec-kit-template/main/.github/skills/spec-kit-requirements-nfr/SKILL.mdgit clone --depth 1 https://github.com/lksnext-ai-lab/spec-kit-templateWrote 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/lksnext-ai-lab/spec-kit-template/spec-kit-requirements-nfr)<a href="https://agentmods.dev/skills/lksnext-ai-lab/spec-kit-template/spec-kit-requirements-nfr"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/spec-kit-requirements-nfr/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/lksnext-ai-lab/spec-kit-template/spec-kit-requirements-nfr"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/spec-kit-requirements-nfr.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.00071 | $0.01115 |
| Opus 5 | $0.00036 | $0.00558 |
| Sonnet 5 | $0.00014 | $0.00223 |
| Haiku 4.5 | $0.00007 | $0.00112 |
Grade A, and why
spec-kit-requirements-nfr 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 12d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Requirements-NFR (spec-kit)
Objetivo
Mantener NFR claros, medibles o verificables, sin suposiciones, y útiles para implementación/validación.
Archivos que se pueden modificar
- Primario:
docs/spec/11-requisitos-tecnicos-nfr.md - Si aplica:
docs/spec/90-infra.md(operación/monitoring/backups)docs/spec/80-seguridad.md(controles)docs/spec/40-arquitectura.md(trade-offs/impacto técnico)docs/spec/adr/ADR-*.md(decisiones con trade-off)docs/spec/95-open-questions.md(gaps)docs/spec/96-todos.md(pendientes)
No tocar otros ficheros salvo petición explícita.
Reglas duras (anti-deriva)
- No inventar umbrales
- No fijar p95, disponibilidad, RTO/RPO, retención, límites de carga, etc. si no están definidos.
- Si son necesarios:
TBD+OPENQ(oTODOsi no bloquea).
- NFR ≠ FR
- Un NFR no describe flujos funcionales ni UI/API concretas; describe condiciones y verificación.
- Vendor-neutral por defecto
- No imponer herramientas/stack salvo evidencia explícita.
- No crear NFR “de catálogo”
- Cada NFR debe tener un driver (riesgo, compliance, coste, escala, UX, operación, etc.). Si no hay driver, no crear el NFR.
- Trade-offs relevantes → ADR
- Cuando cumplir el NFR implica elegir (coste vs retención, latencia vs consistencia, etc.).
Convenciones
- ID:
NFR-###correlativo - Prioridad:
MVP|Should|Could - Estado:
Draft|Validated|Deprecated - Categoría (usa solo si aporta): Seguridad | Disponibilidad/Continuidad | Rendimiento/Escalabilidad | Observabilidad | Privacidad/Legal | Mantenibilidad | Portabilidad | UX/Accesibilidad | Coste
Plantilla obligatoria por NFR
NFR-### — <Título>
Driver: (por qué existe; 1–2 líneas)
Categoría: (opcional)
Prioridad: MVP | Should | Could
Estado: Draft | Validated | Deprecated
Bloquea: Sí | No (si falta dato)
Enunciado: (condición clara, sin adjetivos vacíos)
Métrica (si aplica):
- SLI: (qué se mide)
- Umbral: (valor o
TBD) - Ventana/escenario: (valor o
TBD)
Si hay SLI pero umbral TBD: NO inventar número.
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.
- 12d ago First seen · 100 lines · 71 tokens per session scan A d47fd0a4883a
spec-kit-requirements-nfr is a skill published in the GitHub repository lksnext-ai-lab/spec-kit-template (5 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 71 tokens to every session and 1,115 once invoked, about $0.0004 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.
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…
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…
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…
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…
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…