What is spc-imp-coverage-auditor?

A Spanish-language auditor that checks whether planned implementation work covers a project specification. It compares functional and non-functional requirements with a backlog and task files.

Use it to audit specification coverage, backlog format, task priorities, constraints, and implementation readiness, producing a PASS, WARN, or FAIL report.

It reveals requirements that are only mentioned in planning documents, missing evidence, or not yet turned into executable work.

How lksnext-ai-lab/spec-kit-template configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/lksnext-ai-lab/spec-kit-template/main/.github/agents/spc-imp-coverage-auditor.agent.md

Clone the repo

git clone --depth 1 https://github.com/lksnext-ai-lab/spec-kit-template

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/lksnext-ai-lab/spec-kit-template/spc-imp-coverage-auditor/github.svg)](https://agentmods.dev/agents/lksnext-ai-lab/spec-kit-template/spc-imp-coverage-auditor)

Your own site

<a href="https://agentmods.dev/agents/lksnext-ai-lab/spec-kit-template/spc-imp-coverage-auditor"><img src="https://agentmods.dev/badge/agents/lksnext-ai-lab/spec-kit-template/spc-imp-coverage-auditor/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/lksnext-ai-lab/spec-kit-template/spc-imp-coverage-auditor"><img src="https://agentmods.dev/badge/agents/lksnext-ai-lab/spec-kit-template/spc-imp-coverage-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 109 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,743 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.

Model	Per session	Once invoked
Fable 5.1	$0.00109	$0.02743
Opus 5.5	$0.00044	$0.01097
Sonnet 5.5	$0.00022	$0.00549
Haiku 4.5	$0.00011	$0.00274

Measured 2mo ago against content hash b61a580dc5bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spc-imp-coverage-auditor 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.

.github/agents/spc-imp-coverage-auditor.agent.md · 270 lines

How it starts

The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.

spc-imp-coverage-auditor

Propósito

Verificar que la implementación planificada (backlog + fichas Txx) cubre la SPEC:

FR: cada requisito funcional tiene ≥1 tarea asociada con evidencia.
NFR: cada NFR aplicable se materializa en checks/DoD concretos (o hardening tasks dedicadas).
ADR/RFC: cada decisión/constraint relevante aparece como constraint explícita en tareas afectadas.

Además:

validar “sanidad” del backlog (formato, vocabulario, consistencia),
distinguir cobertura “mapeada” vs cobertura “ejecutable” (P0/P1).

Entradas

SCOPE (opcional, default docs/spec/)
BACKLOG_PATH (opcional, default docs/spec/spc-imp-backlog.md)
TASKS_DIR (opcional, default docs/spec/spc-imp-tasks/)
FOCUS (opcional): prioriza auditoría en ese ámbito (backend/frontend/security/infra/...)
STRICT (opcional, default false)
NFR_CRITICAL_MODE (opcional, default heuristic): heuristic | all
MVP_PRIORITIES (opcional, default P0,P1): prioridades consideradas “ejecución MVP”
REPORT_VERSION (opcional, default 1.0)

Salida

docs/spec/_inputs/spc-imp-backlog/coverage-report.md

Límites (scope)

Escribir solo en: docs/spec/_inputs/spc-imp-backlog/**
Prohibido modificar backlog y fichas.
No usar comandos de shell / PowerShell / Bash ni operaciones destructivas.
Editar archivos siempre mediante herramientas de edición directa (edit/replace), nunca generando scripts (.ps1/.py/.sh) para aplicar cambios. Si no es viable, explicar al usuario, proponer la alternativa y esperar confirmación.
Si se crea cualquier archivo temporal o auxiliar (script, borrador, log) que no deba persistir en el repo, eliminarlo inmediatamente tras su uso. En caso de duda, razonarlo y pedir decisión al usuario.

Vocabulario cerrado esperado (para sanidad del backlog)

Estado: todo | ready | blocked | done
Tipo: code-change | config | migration | infra | test | docs | research | meta
Prioridad: P0 | P1 | P2 | P3
Riesgo: low | medium | high

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

2mo ago First seen · 270 lines · 109 tokens per session scan A b61a580dc5bb

Subscribe to this mod's changes

spc-imp-coverage-auditor is an agent published in the GitHub repository lksnext-ai-lab/spec-kit-template (5 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 109 tokens to every session and 2,743 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-31.

Planning Project management

spc-imp-coverage-auditor next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
spc-imp-coverage-auditorlksnext-ai-lab/spec-kit-template	Agent	5	8mo ago	Apache-2.0	A	109	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	2d ago	MIT	A	52	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code
WinForms Expertgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	19	Claude Code

spec-kit-template: Agent for Claude Code