spec-kit-template: Agent for Claude Code

.github/agents/spc-spec-planner.agent.md

spc-spec-planner is an agent for Claude Code from lksnext-ai-lab/spec-kit-template. It costs 102 tokens per session (1,984 once invoked), scanned A, original, Apache-2.0.

A specification-planning agent that maintains `docs/spec/01-plan.md` as the executable plan for the current iteration. It breaks work into small tasks with clear completion checks and marks decisions that still need answers.

In plain words
What is it for?
Use it to define an iteration goal, split work into atomic blocks, set scope boundaries, and identify open questions or decisions before writing the specification.
Why use it?
It turns a broad specification effort into a short, ordered set of tasks. This helps teams see what is in scope, what is blocked, and what evidence is needed.

Agent for Claude Code

Written for Claude Code: user-invocable in frontmatter.

This is lksnext-ai-lab/spec-kit-template's own configuration. It tells Claude Code how to work on spec-kit-template itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything spec-kit-template configures →

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-spec-planner.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.

agentmods badge for spc-spec-planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/lksnext-ai-lab/spec-kit-template/spc-spec-planner/github.svg)](https://agentmods.dev/agents/lksnext-ai-lab/spec-kit-template/spc-spec-planner)
Your own site
<a href="https://agentmods.dev/agents/lksnext-ai-lab/spec-kit-template/spc-spec-planner"><img src="https://agentmods.dev/badge/agents/lksnext-ai-lab/spec-kit-template/spc-spec-planner/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.

agentmods 80×15 button for spc-spec-planner

Your own site · 80×15
<a href="https://agentmods.dev/agents/lksnext-ai-lab/spec-kit-template/spc-spec-planner"><img src="https://agentmods.dev/badge/agents/lksnext-ai-lab/spec-kit-template/spc-spec-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,984 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00102 $0.01984
Opus 5 $0.00051 $0.00992
Sonnet 5 $0.00020 $0.00397
Haiku 4.5 $0.00010 $0.00198

Measured 9d ago against content hash 6ee2386c2335, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

spc-spec-planner 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 9d 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-spec-planner.agent.md · 179 lines

How it starts

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

spc-spec-planner — planificación de la especificación (iteración activa)

Objetivo

Mantener docs/spec/01-plan.md como plan ejecutable de la iteración activa (no backlog):

  • Objetivo de iteración (qué se considera “cerrado”)
  • Alcance IN/OUT
  • Bloques atómicos (compatibles con ejecución stepper)
  • 5–15 tareas atómicas con DoD verificable
  • Gates visibles: OPENQ / DECISION / RFC needed

Este agente NO redacta en profundidad (eso es Writer) y NO “cierra decisiones” (eso es Reviewer/RFC).


Reglas duras (operación segura)

  • Ignora completamente docs/spec/history/** (no leer/editar/usar 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.
  • No inventes requisitos ni detalles técnicos. Si falta info: crea/actualiza OPENQ-###.
  • Diff-friendly: si 01-plan.md ya existe, evita cambios cosméticos; toca solo lo necesario.

Regla especial: 01-plan.md solo iteración activa

  • Si detectas que docs/spec/01-plan.md contiene iteraciones cerradas mezcladas, NO lo limpies.
  • Detén la planificación y recomienda ejecutar /close-iteration para archivar y reabrir plan limpio.

Política de “STOP” (para no planificar en falso)

Si hay incertidumbre crítica sin evidencia (BLOCKER), el plan debe reflejarlo:

  • Seguridad/auth/roles/secrets/datos sensibles/integraciones críticas/NFR críticos
    • ⇒ crear/actualizar OPENQ
    • ⇒ marcar tareas como BLOCKED
    • ⇒ si el tema requiere formalización: gate RFC needed

Prohibido marcar READY algo que dependa de suposiciones críticas.

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

  1. 9d ago First seen · 179 lines · 102 tokens per session scan A 6ee2386c2335

Subscribe to this mod's changes

spc-spec-planner 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 102 tokens to every session and 1,984 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.