Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add gethouston/houston --skill redactar-un-playbookgit clone --depth 1 https://github.com/gethouston/houstonWrote 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/gethouston/houston/redactar-un-playbook)<a href="https://agentmods.dev/skills/gethouston/houston/redactar-un-playbook"><img src="https://agentmods.dev/badge/skills/gethouston/houston/redactar-un-playbook/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/gethouston/houston/redactar-un-playbook"><img src="https://agentmods.dev/badge/skills/gethouston/houston/redactar-un-playbook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00093 | $0.01793 |
| Opus 5 | $0.00046 | $0.00897 |
| Sonnet 5 | $0.00019 | $0.00359 |
| Haiku 4.5 | $0.00009 | $0.00179 |
Grade A, and why
redactar-un-playbook 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Redactar un playbook
Cuándo usarlo
- "redacta el playbook de P1" / "runbook para cortes de servicio" / "playbook de incidente de seguridad."
- Después de un incidente donde dices "necesitamos un playbook de verdad para esto."
- Cuando el onboarding marca la respuesta a incidentes como
TBD.
Conexiones que necesito
Ejecuto el trabajo externo a través de Composio. Antes de que esta skill se ejecute, verifico que las categorías de abajo estén conectadas. Si falta alguna, nombro la categoría, te pido que la conectes desde la pestaña de Integraciones, y me detengo.
- Mensajería (Slack / Microsoft Teams): canal interno con nombre para el paso de "los primeros 15 minutos". Obligatorio.
- Seguimiento de desarrollo (GitHub / Linear): destino con nombre para el traspaso a ingeniería y el seguimiento del post-mortem. Obligatorio.
Si ninguna está conectada, me detengo y te pido que conectes primero Slack (o Teams): el playbook depende de un canal interno real.
Información que necesito
Primero leo tu contexto de soporte. Por cada campo obligatorio que falte, te hago UNA pregunta en lenguaje sencillo (mejor modalidad: app conectada > archivo > URL > texto pegado) y espero.
- Definición de severidad para este tipo de incidente: Obligatorio. Por qué la necesito: la línea de disparo al inicio del playbook necesita un límite real. Si falta, pregunto: "¿Qué cuenta como un P1 para ti? Dame 2 o 3 tickets de ejemplo que calificarían."
- Turno de guardia + contactos con nombre: Obligatorio. Por qué la necesito: el playbook llama a personas reales, no a "ingeniería" en general. Si falta, pregunto: "¿Quién está de guardia en ingeniería cuando algo se rompe a las 2am, y cómo lo contactas?"
- Lista VIP: Obligatorio. Por qué la necesito: los VIP reciben un mensaje uno a uno durante los incidentes, no un correo masivo. Si falta, pregunto: "¿Cuáles 3 a 5 clientes deberían recibir siempre una nota personal tuya cuando hay un incidente?"
- Página de estado / canal público de comunicación: Opcional. Por qué la necesito: el paso de "los primeros 15 minutos" la cambia a en investigación. Si no la tienes, sigo con TBD.
- Voz para la comunicación con clientes: Opcional. Por qué la necesito: las plantillas de incidentes se leen más genuinas en tu tono. Si no la tienes, sigo con TBD y recomiendo ejecutar la calibración de voz.
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.
- 9d ago First seen · 121 lines · 93 tokens per session scan A b2f3c232d7f2
redactar-un-playbook is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 1,793 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…