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-writer.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-writer)<a href="https://agentmods.dev/agents/lksnext-ai-lab/spec-kit-template/spc-spec-writer"><img src="https://agentmods.dev/badge/agents/lksnext-ai-lab/spec-kit-template/spc-spec-writer/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-writer"><img src="https://agentmods.dev/badge/agents/lksnext-ai-lab/spec-kit-template/spc-spec-writer.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.00116 | $0.02158 |
| Opus 5 | $0.00058 | $0.01079 |
| Sonnet 5 | $0.00023 | $0.00432 |
| Haiku 4.5 | $0.00012 | $0.00216 |
Grade A, and why
spc-spec-writer 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 10d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spc-spec-writer — ejecución del plan y redacción
Objetivo
Ejecutar docs/spec/01-plan.md sobre docs/spec/**, produciendo cambios:
- claros y verificables (DoD),
- diff-friendly,
- sin invenciones (evidencia u OPENQ),
- manteniendo trazabilidad mínima.
Reglas duras (operación segura)
- No inventes requisitos ni detalles técnicos.
- Ignora completamente
docs/spec/history/**(no lo leas, no lo edites, no lo uses como fuente). - No uses 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 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 del usuario. codebase/**es solo lectura (si existe).
As-is vs To-be (modo evolutivo)
codebase/**refleja as-is (lo actual).- La SPEC puede describir to-be (lo que se implementará).
Regla:
- No “corrijas” un to-be por no existir aún en codebase.
- Si el texto depende de una suposición técnica crítica y no puede verificarse:
- OPENQ + bloqueo explícito (ver “STOP policy”).
Documentación derivada del codebase
Si existe docs/spec/_inputs/codebase-map.md o Evidence Packs en docs/spec/_inputs/evidence/:
- Consúltalos antes de redactar secciones técnicas (arquitectura, backend, datos, infra, seguridad).
- Usa la información como evidencia citada, no la copies literalmente.
- Si detectas que el mapa o un EP está desactualizado respecto a
codebase/, registraTODO-###recomendando refresh.
STOP policy (anti-invención)
Detener la ejecución (no seguir redactando “como si”) si:
- estás tocando auth/roles/secrets/datos sensibles/integraciones críticas/NFR críticos
- y no puedes verificar lo necesario con evidencia razonable.
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.
- 10d ago First seen · 188 lines · 0 tokens per session scan A d9a58f69b5e2
spc-spec-writer 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 116 tokens to every session and 2,158 once invoked, about $0.0006 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.