What is spec-kit-template codebase.instructions.md?

A set of repository instructions for the `codebase/` directory, which contains the existing application code used as evidence during specification work. It requires that this directory be read-only and that technical claims cite concrete file paths.

Use it when inspecting the current implementation to confirm its stack, modules, endpoints, models, permissions, or flows, and when documenting evidence or unresolved questions.

It prevents specification work from changing the existing code while encouraging decisions based on what the code actually contains. Missing evidence must be recorded as an open question.

How lksnext-ai-lab/spec-kit-template configures GitHub Copilot

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/instructions/codebase.instructions.md

Clone the repo

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

Made for: GitHub Copilot.

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/instructions/lksnext-ai-lab/spec-kit-template/codebase/github.svg)](https://agentmods.dev/instructions/lksnext-ai-lab/spec-kit-template/codebase)

Your own site

<a href="https://agentmods.dev/instructions/lksnext-ai-lab/spec-kit-template/codebase"><img src="https://agentmods.dev/badge/instructions/lksnext-ai-lab/spec-kit-template/codebase/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/instructions/lksnext-ai-lab/spec-kit-template/codebase"><img src="https://agentmods.dev/badge/instructions/lksnext-ai-lab/spec-kit-template/codebase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 565 This file is loaded in full into every session.

When invoked 565 The same file — it is already loaded in full.

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.00565	$0.00565
Opus 5.5	$0.00226	$0.00226
Sonnet 5.5	$0.00113	$0.00113
Haiku 4.5	$0.00056	$0.00056

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

Security

Grade A, and why

spec-kit-template codebase.instructions.md 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/instructions/codebase.instructions.md · 69 lines

How it starts

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

Codebase instructions (codebase/**)

Estas instrucciones aplican al repositorio de código cuando está presente en el workspace como codebase/**.

Regla 0: SOLO LECTURA

codebase/** es read-only.
No crear, borrar ni modificar archivos en codebase/**.
Cualquier cambio a implementar se describe en docs/spec/** o en tareas SPC-IMP, pero no se aplica aquí.

Objetivo del modo evolutivo

Usar el codebase como fuente de verdad as-is para:

confirmar stack, módulos y arquitectura real,
encontrar endpoints, modelos, permisos, flujos,
fundamentar decisiones y requisitos,
evitar inventar.

Protocolo de evidencia

Cuando se afirme algo técnico sobre el as-is:

Citar evidencia con rutas concretas:
- codebase/<ruta/al/archivo> (+ clase/función relevante)
Si la evidencia es amplia o compleja:
- crear un Evidence Pack en docs/spec/_inputs/evidence/EP-###-<tema>.md
- y enlazarlo desde la spec
Si tras buscar no hay evidencia suficiente:
- registrar OPENQ-### indicando:
  - qué se intentó verificar
  - dónde se buscó (rutas y términos)
  - qué falta para cerrar la duda

Buenas prácticas de búsqueda

Buscar por:
- nombres de endpoints/routers/controllers
- nombres de servicios (*Service)
- permisos/roles (permission, scope, role, policy)
- entidades/modelos (ORM)
- configuración (env, settings, config, yaml)
Revisar:
- módulos “core” y “infra”
- tests si existen
- documentación interna del repo

Qué producir a partir del codebase (outputs típicos)

docs/spec/_inputs/codebase-map.md (mapa técnico resumido)
Evidence Packs en docs/spec/_inputs/evidence/
OPENQ-### en docs/spec/95-open-questions.md cuando falte evidencia

Prohibiciones (anti-invención)

No “deducir” implementaciones no vistas.
No asumir que un patrón existe “porque suele existir”.
No afirmar que un endpoint existe si no se encuentra.
No describir modelos/campos sin evidencia.

Read the full file on GitHub · 69 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 · 69 lines · 565 tokens per session scan A 30676af3dbe8

Subscribe to this mod's changes

spec-kit-template codebase.instructions.md is an instructions file published in the GitHub repository lksnext-ai-lab/spec-kit-template (5 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 565 tokens to every session, about $0.0023 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.

spec-kit-template codebase.instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
spec-kit-template codebase.instructions.mdlksnext-ai-lab/spec-kit-template	Instructions file	5	8mo ago	Apache-2.0	A	565	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

spec-kit-template: Instructions file for GitHub Copilot