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-maintenance/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-maintenance)<a href="https://agentmods.dev/skills/lksnext-ai-lab/spec-kit-template/spec-kit-codebase-maintenance"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/spec-kit-codebase-maintenance.svg" alt="Measured on agentmods" 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.01037 |
| Opus 5 | $0.00000 | $0.00518 |
| Sonnet 5 | $0.00000 | $0.00207 |
| Haiku 4.5 | $0.00000 | $0.00104 |
Grade A, and why
spec-kit-codebase-maintenance 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: codebase_maintenance
Objetivo
Definir cuándo y cómo actualizar la documentación derivada del codebase
(codebase-map.md y Evidence Packs) tras cambios en codebase/**,
evitando burocracia innecesaria.
Este skill lo consume spc-codebase-discovery (modo refresh) y el Director
(para decidir si proponer refresh post-implementación).
Principios
- Mantenimiento proporcional: solo actualizar lo impactado por el cambio real.
- Sin burocracia: refactors internos sin cambio funcional NO requieren actualización.
- Diff-friendly: nunca reescribir el mapa/EP completo; solo secciones afectadas.
- Opt-in: la actualización es una sugerencia del Director, no una obligación automática.
Señales de obsolescencia
El Director o los agentes pueden detectar obsolescencia mediante:
- Fecha:
last_updatedencodebase-map.md> 60 días → WARN. - Cruce de áreas: si una tarea Txx completada (tipo
code-changeomigration) opera sobre un área listada enareas_covereddel mapa → sugerir refresh. - OPENQ resuelta: si se cierra una OPENQ que referenciaba el mapa o un EP, verificar si esa resolución afecta al contenido documentado.
Tabla de actualización: tipo de cambio → acción
| Tipo de cambio en codebase | Acción sobre codebase-map.md |
Acción sobre Evidence Packs |
|---|---|---|
| Nuevo módulo/servicio | Añadir sección en "Módulos/capacidades" | Recomendar EP si es crítico (auth/datos/integración) |
| Cambio de stack/framework | Actualizar "Stack y tooling" | Actualizar EP de stack si existe |
| Nuevo endpoint/API | Actualizar "Interfaces públicas" | EP solo si es integración externa |
| Cambio de modelo de datos/migraciones | Actualizar "Persistencia" | Actualizar EP de datos si existe |
| Cambio de auth/roles/permisos | Actualizar sección relevante | Actualizar o crear EP (tema crítico) |
| Cambio de CI/CD o infra | Actualizar "Operación" | EP solo si afecta a despliegue |
| Nuevo entrypoint | Actualizar "Entrypoints y bootstrap" | No requiere EP |
| Cambio de config/env | Actualizar "Operación" (config) | No requiere EP salvo secretos |
| Refactor interno (sin cambio funcional) | No tocar | No tocar |
| Renombrado de módulos (sin cambio funcional) | Actualizar nombres/rutas en secciones afectadas | Actualizar rutas en EPs afectados |
| Eliminación de módulos | Eliminar/marcar sección del módulo | Marcar EP como obsoleto si aplica |
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 · 103 lines · 0 tokens per session scan A 559fda0a3155
spec-kit-codebase-maintenance 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,037 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…