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-infra/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-infra)<a href="https://agentmods.dev/skills/lksnext-ai-lab/spec-kit-template/spec-kit-infra"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/spec-kit-infra/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-infra"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/spec-kit-infra.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.00063 | $0.01664 |
| Opus 5 | $0.00032 | $0.00832 |
| Sonnet 5 | $0.00013 | $0.00333 |
| Haiku 4.5 | $0.00006 | $0.00166 |
Grade A, and why
spec-kit-infra 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 11d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Infra (spec-kit)
Objetivo
Dejar docs/spec/90-infra.md operable y verificable para MVP, sin suposiciones:
- Entornos (DEV/PRE/PROD o los que existan)
- CI/CD y estrategia de release
- Despliegue + verificación post-deploy + rollback
- Observabilidad mínima (logs/métricas/alertas)
- Backups/DR + restore (y pruebas)
- Accesos/secretos/hardening
- Coste (drivers + controles básicos)
Cuándo usar
- Cuando la spec ya define qué construir y falta “cómo operarlo”.
- Antes de empezar implementación/release para evitar sorpresas (rollback, backups, alertas, accesos).
- En cambios que afecten despliegue, datos, seguridad operativa u observabilidad.
Archivos que se pueden modificar
- Primario:
docs/spec/90-infra.md - Si aplica:
docs/spec/adr/ADR-*.md(decisiones infra/ops con trade-offs)docs/spec/95-open-questions.md(gaps críticos)docs/spec/96-todos.md(pendientes no bloqueantes)
No tocar otros ficheros de
docs/spec/**salvo petición explícita del usuario.
Fuentes típicas (leer antes)
docs/spec/11-requisitos-tecnicos-nfr.mddocs/spec/40-arquitectura.mddocs/spec/80-seguridad.mddocs/spec/60-backend.md/docs/spec/70-frontend.md- Evidence Packs
docs/spec/_inputs/evidence/
Reglas duras
- No inventar
- No fijar RTO/RPO, retención, SLAs, herramientas concretas, cloud/on-prem, tamaños o volúmenes si no están en la spec/evidencia.
- Si falta un dato crítico →
OPENQ:y enlazar adocs/spec/95-open-questions.md.
- Vendor-neutral por defecto
- Describir patrones (“blue/green”, “rolling”, “secrets manager”) sin imponer proveedor/stack.
- Si el proveedor/stack existe en la spec, entonces sí: referenciarlo.
- No secretos
- Nunca incluir valores reales (keys, tokens, passwords, endpoints privados). Solo “existe X” + dónde se configura.
- Trade-offs relevantes → ADR Crear ADR cuando se elige entre opciones con impacto:
- estrategia de despliegue (rolling vs blue/green vs gates manuales),
- estrategia de secretos,
- retención de logs/costes,
- DR/restore,
- política de accesos (break-glass, MFA, segregación).
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.
- 11d ago First seen · 155 lines · 63 tokens per session scan A 1c01da12e0c3
spec-kit-infra 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 adds 63 tokens to every session and 1,664 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.
Other skills, from other repositories
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-version
Atmos Version Tracker: version tracks, lock files, managed external dependency versions, atmos version track commands, !version, file managers, update policy, pinning, and CI verification.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.