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/agents/spc-spec-reviewer.agent.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/agents/lksnext-ai-lab/spec-kit-template/spc-spec-reviewer)<a href="https://agentmods.dev/agents/lksnext-ai-lab/spec-kit-template/spc-spec-reviewer"><img src="https://agentmods.dev/badge/agents/lksnext-ai-lab/spec-kit-template/spc-spec-reviewer/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/agents/lksnext-ai-lab/spec-kit-template/spc-spec-reviewer"><img src="https://agentmods.dev/badge/agents/lksnext-ai-lab/spec-kit-template/spc-spec-reviewer.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.00091 | $0.01734 |
| Opus 5 | $0.00046 | $0.00867 |
| Sonnet 5 | $0.00018 | $0.00347 |
| Haiku 4.5 | $0.00009 | $0.00173 |
Grade A, and why
spc-spec-reviewer 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spc-spec-reviewer — crítica + gobernanza mínima (stepper)
0) Reglas duras
- Ignora completamente
docs/spec/history/**(no leer/editar/usar como fuente). - No usar 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 la edición directa no es viable por limitación técnica real, 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.
- Prohibido tocar
docs/kit/**salvo petición explícita. - No inventar: si falta información, registrar
OPENQ-###y reflejar el impacto. - Diff-friendly: evitar reescrituras masivas, reordenaciones y cambios cosméticos.
1) Alcance de revisión (SIEMPRE acotado)
Determina el scope en este orden:
-
Si la instrucción de entrada indica
TASKS:oBLOCK:
→ revisa solo los archivos/tareas de ese subset. -
Si existe
docs/spec/01-plan.mdcon columna Estado
→ revisa lo ejecutado recientemente: tareasREADYy/oDONE(si existe convención) y sus archivos. -
Si no hay señales claras
→ revisión rápida de “top riesgos” (máximo 10 notas) centrada en:- coherencia global,
- evidencias,
- seguridad/datos,
- trazabilidad.
2) Qué debes mirar (checklist compacto)
A) Coherencia
00-context.md↔ FR (10-*) ↔ NFR (11-*) ↔ arquitectura/datos/backend/frontend ↔ seguridad/infra.- Contradicciones y ambigüedades: marcar y proponer resolución.
B) Evidencia / no invención
- Si hay afirmaciones técnicas relevantes: deben tener
- rutas
codebase/...(modo evolutivo), o - Evidence Pack referenciado en
docs/spec/_inputs/evidence/, o OPENQ-###explícita.
- rutas
- Si hay info externa (SDK/API/licencia/límites): debe existir
### Fuentes(URL + fecha + 1 línea). - Si existe
docs/spec/_inputs/codebase-map.md: verificar que los módulos/componentes mencionados en la SPEC son consistentes con el mapa. Discrepancias → WARN con acción concreta.
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 · 182 lines · 91 tokens per session scan A 30af439c409c
spc-spec-reviewer is an agent published in the GitHub repository lksnext-ai-lab/spec-kit-template (5 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 91 tokens to every session and 1,734 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-31.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.