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-rfc-proposal/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-rfc-proposal)<a href="https://agentmods.dev/skills/lksnext-ai-lab/spec-kit-template/spec-kit-rfc-proposal"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/spec-kit-rfc-proposal/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-rfc-proposal"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/spec-kit-rfc-proposal.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.00000 | $0.01674 |
| Opus 5 | $0.00000 | $0.00837 |
| Sonnet 5 | $0.00000 | $0.00335 |
| Haiku 4.5 | $0.00000 | $0.00167 |
Grade A, and why
spec-kit-rfc-proposal 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: rfc-proposal
Propósito
Crear/actualizar un RFC narrativo en español que resuma y conecte la especificación distribuida en docs/spec/**, sin sustituirla.
El RFC sirve para:
- Alinear stakeholders (qué se va a hacer y por qué).
- Consolidar decisiones (ADRs) y trade-offs.
- Identificar riesgos y gaps (OPENQ) sin “rellenar”.
Inputs (mínimo)
ROOT_SPEC_DIR:docs/spec/RFC_ID(opcional):RFC-0001,RFC-0002, ...SLUG(opcional): texto corto del cambio (kebab-case)VARIANTE(opcional):architecture(default) |executiveFOCUS(opcional): 3–8 bullets con énfasis (p.ej. “seguridad”, “operación”, “migración”, “frontend”).
Outputs (obligatorio)
-
RFC Markdown en
docs/spec/rfc/:architecture:docs/spec/rfc/<RFC_ID>-<slug>.mdexecutive:docs/spec/rfc/<RFC_ID>-<slug>-executive.md
-
Sección final “Fuentes utilizadas” con listado de ficheros
docs/spec/**consultados y motivo (1 línea c/u).
Opcional (solo si el repositorio ya lo está usando): crear/actualizar
docs/spec/_inputs/rfc/<RFC_ID>/sources.mdcon el mismo listado de fuentes.
Hard rules (no negociables)
-
Idioma: todo en español.
-
No inventar
- No afirmar hechos/decisiones/cifras/contratos/SLAs/endpoints si no están en
docs/spec/**. - Si falta evidencia: escribir
OPENQ:y enlazar a../95-open-questions.md(o indicar dónde debe crearse).
- Separación as-is / to-be
- “Confirmado (as-is)” solo si hay evidencia explícita en spec.
- “Propuesta / decisión” debe quedar claramente como tal.
- Si es hipótesis: marcar
HIPÓTESIS:o convertir enOPENQsi es crítica.
- Evidencias por sección
- Cada sección del RFC termina con:
**Evidencias:**+ links relativos (mín. 1).
- Secciones críticas (seguridad/operación/migración/alternativas) requieren ≥2 evidencias si existen fuentes.
- Contradicciones
- Si dos fuentes se contradicen:
DISCREPANCIA:+ descripción + links a ambas.- Si bloquea decisión:
OPENQ.
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 · 206 lines · 0 tokens per session scan A b28ac6ac3b1e
spec-kit-rfc-proposal 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 costs nothing until one of its globs matches a file; then it loads 1,674 tokens. 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
plan-authoring
Reference material for writing implementation plans (technical context, architecture decisions, data models, API contracts, project-instructions alignment). Loaded on demand by plan-feature; not directly invokable.
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
adr-authoring
Defines the canonical MADR format, lifecycle rules, numbering policy, and SAD catalog contract for standalone ADRs under specs/adrs/.
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
game-ui-product-design
A planning workflow for a game before its interface visuals are generated. It produces a game design document, product requirements document, and interaction logic document.
game-ui-sprite-sheet-splitter
Splits a generated game UI sprite sheet or component board into individual transparent PNG elements, writes crop metadata, validates dimensions and alpha channels, and packages all PNG files into a ZIP archive. Use after component breakdown when users ask to cut a combined sprite sheet, isolate every…