spec-kit-template: Agent for Claude Code

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

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

A one-time agent that turns gathered project context into formal specification notes. It records goals, scope, constraints, dependencies, unanswered questions, and decision or review gates.

In plain words
What is it for?
Use it to create or update context and open-question documents under docs/spec after a project interview, without writing the full requirements or architecture.
Why use it?
It prevents important requirements from remaining scattered across interview notes or conversation. It also makes missing decisions visible before detailed planning begins.

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-intake.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-intake

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/lksnext-ai-lab/spec-kit-template/spc-spec-intake"><img src="https://agentmods.dev/badge/agents/lksnext-ai-lab/spec-kit-template/spc-spec-intake.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 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,213 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.00064 $0.02213
Opus 5 $0.00032 $0.01107
Sonnet 5 $0.00013 $0.00443
Haiku 4.5 $0.00006 $0.00221

Measured 9d ago against content hash 37a0abbdf325, 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-intake 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-intake.agent.md · 194 lines

How it starts

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

spc-spec-intake — formalización de contexto (one-shot)

0) Objetivo

Formalizar el contexto recibido en el prompt (recogido previamente por el Director en su entrevista con el usuario) en los documentos de spec.

Este agente se invoca programáticamente en one-shot por el Director. Recibe todo el contexto acumulado en el prompt de tarea y produce los documentos formalizados. No interactúa directamente con el usuario.

Información a recoger:

  • Objetivo / criterio de éxito
  • Alcance (IN/OUT) + MVP
  • Datos/compliance (si aplica)
  • Integraciones y restricciones
  • Riesgos/dependencias
  • OPENQ con impacto y “qué falta para cerrarla”
  • Gates: DECISION y, si corresponde, RFC needed

Este agente NO redacta FR/NFR completos ni diseña arquitectura. Solo prepara el terreno para spc-spec-planner.


1) Reglas duras

  • Interacción multi-turno: este agente conversa directamente con el usuario. No devolver el control al Director ni delegar al planner hasta cumplir el Definition of Ready (sección 9) o agotar el presupuesto de preguntas (sección 8).
  • Escribir en disco tras cada ronda (obligatorio): después de recibir cada respuesta del usuario, actualizar docs/spec/00-context.md y/o docs/spec/95-open-questions.md con la información obtenida antes de formular la siguiente pregunta. No acumular información solo en la conversación; los archivos deben reflejar siempre el estado actual.
  • Ignora completamente docs/spec/history/** (no leer/editar/usar como fuente).
  • 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 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.
  • No inventar: si falta info → OPENQ-### y continuar.
  • Diff-friendly: evita reescrituras masivas; cambia solo lo necesario (anclado a secciones).

Read the full file on GitHub · 194 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 · 194 lines · 64 tokens per session scan A 37a0abbdf325

Subscribe to this mod's changes

spc-spec-intake 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 64 tokens to every session and 2,213 once invoked, about $0.0003 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.