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/skills/spec-kit-codebase-scout/SKILL.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/skills/lksnext-ai-lab/spec-kit-template/spec-kit-codebase-scout)<a href="https://agentmods.dev/skills/lksnext-ai-lab/spec-kit-template/spec-kit-codebase-scout"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/spec-kit-codebase-scout/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/skills/lksnext-ai-lab/spec-kit-template/spec-kit-codebase-scout"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/spec-kit-codebase-scout.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.00000 | $0.01638 |
| Opus 5 | $0.00000 | $0.00819 |
| Sonnet 5 | $0.00000 | $0.00328 |
| Haiku 4.5 | $0.00000 | $0.00164 |
Grade A, and why
spec-kit-codebase-scout 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 8d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: codebase_scout
Objetivo
Explorar codebase/** (solo lectura) para construir/actualizar un mapa técnico as-is útil para el flujo SPEC (plan/write/review), minimizando el riesgo de inventar.
Output principal:
docs/spec/_inputs/codebase-map.md
Outputs secundarios (si aplica):
docs/spec/95-open-questions.md(OPENQ-### nuevas cuando falte evidencia)- Recomendación de Evidence Pack cuando el tema requiera profundidad (
evidence_pack).
Principios
- Read-only: nunca modificar
codebase/**. - Evidencia primero: afirmaciones técnicas relevantes deben estar sustentadas con rutas concretas.
- No inventar: si no se confirma, se registra
OPENQ. - Mapa operativo: síntesis accionable, no enciclopedia.
- Seguridad: no copiar secretos (tokens, API keys, credenciales,
.envreales).
Entradas
codebase/**(solo lectura)- (Opcional) Pistas del usuario: rutas, módulos, términos, servicios
- (Opcional) Evidence Packs existentes:
docs/spec/_inputs/evidence/
Salidas
docs/spec/_inputs/codebase-map.md(crear/actualizar)OPENQ-###endocs/spec/95-open-questions.mdsi hay gaps críticos- (Opcional) “Recomendación EP”: listar qué Evidence Packs conviene generar y por qué
Timeboxing (obligatorio)
Elegir un modo (por defecto: Quick):
Quick scan (15–30 min)
- Stack + tooling
- Entry point(s)
- Estructura de carpetas (alto nivel)
- 5–10 módulos/capacidades con evidencia mínima
- Persistencia (BBDD/ORM/migraciones) si se encuentra rápido
- CI/tests (mención breve)
Deep scan (60–90 min)
Además de lo anterior:
- Interfaces públicas (punto de definición de rutas o resumen por familias)
- Jobs/workers/cron/colas (si existen)
- Logging/observabilidad/config más detallado
- 10–20 módulos/capacidades con evidencias
Si el timebox se agota:
- priorizar completar DoD mínimo y abrir
OPENQen lo crítico.
Reglas duras (hard rules)
- Prohibido modificar codebase
- Evidencia estándar
- Cada afirmación importante debe incluir
EVIDENCE:con rutascodebase/... - Si no hay evidencia, no se formula como hecho →
OPENQ.
- Cada afirmación importante debe incluir
- Sin secretos
- No copiar valores de
.env/secrets ni tokens. A lo sumo: “existe.env.example/ variable X”.
- No copiar valores de
- Confianza
- No usar “probablemente”. O está confirmado con evidencia, o se formula como
OPENQ.
- No usar “probablemente”. O está confirmado con evidencia, o se formula como
- Cambios diff-friendly
- Actualizar por secciones sin reescrituras masivas.
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.
- 8d ago First seen · 204 lines · 0 tokens per session scan A e2c8d0bc44a4
spec-kit-codebase-scout is a skill published in the GitHub repository lksnext-ai-lab/spec-kit-template (5 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,638 tokens. 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 skills, from other repositories
plan-authoring
Reference material for writing implementation plans (technical context, architecture decisions, data models, API contracts, project-instructions alignment). Loaded on demand by plan-feature; not directly invokable.
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
adr-authoring
Defines the canonical MADR format, lifecycle rules, numbering policy, and SAD catalog contract for standalone ADRs under specs/adrs/.
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
game-ui-workflow
Orchestrates an end-to-end game UI workflow from game design (GDD), PRD, and UI interaction logic through design specification, screen-system extension, page image generation, component breakdown, sprite-sheet splitting, PNG ZIP packaging, atlas packing, engine JSON handoff, asset registration, and validation. Use…
game-ui-sprite-sheet-splitter
Splits a generated game UI sprite sheet or component board into individual transparent PNG elements, writes crop metadata, validates dimensions and alpha channels, and packages all PNG files into a ZIP archive. Use after component breakdown when users ask to cut a combined sprite sheet, isolate every…