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 registrar-una-decisiongit 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/registrar-una-decision)<a href="https://agentmods.dev/skills/gethouston/houston/registrar-una-decision"><img src="https://agentmods.dev/badge/skills/gethouston/houston/registrar-una-decision/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/registrar-una-decision"><img src="https://agentmods.dev/badge/skills/gethouston/houston/registrar-una-decision.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.00075 | $0.01673 |
| Opus 5 | $0.00037 | $0.00837 |
| Sonnet 5 | $0.00015 | $0.00335 |
| Haiku 4.5 | $0.00007 | $0.00167 |
Grade A, and why
registrar-una-decision 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Registrar una decisión
Cuándo usarla
- El usuario dice "decidimos", "registra la decisión sobre", "captura esa decisión", "haz un ADR de esto".
- Las notas de reunión pegadas o conectadas contienen un patrón claro de decisión.
- El usuario pide revisar el backlog de decisiones abiertas; la skill también marca las filas
pendingcomodecidedcuando el usuario las declara.
Conexiones que necesito
Ejecuto todo el trabajo externo a través de Composio. Antes de ejecutar esta skill verifico que las categorías de abajo estén vinculadas. Si falta alguna → nombro la categoría, te pido conectarla desde la pestaña de Integraciones y me detengo.
- Grabador de reuniones (Fireflies, Gong) - Opcional. Me permite extraer una transcripción cuando dices "registra la llamada que acabamos de tener". Si no está conectado, trabajo con lo que pegues.
- Documentos / notas (Notion, Google Docs) - Opcional. Si tienes un registro de decisiones o un documento RACI en otro lado, lo leo antes de redactar.
Esta skill funciona sin ninguna conexión. Aquí nunca me bloqueo; en el peor de los casos, tú describes la decisión y yo la capturo.
Información que necesito
Primero leo tu contexto de operaciones. Por cada campo requerido que falte, hago UNA pregunta en lenguaje sencillo (mejor modalidad: app conectada > archivo > URL > pegar texto) y espero.
- La decisión en sí - Requerido. Por qué la necesito: capturo una decisión específica, no la genero. Si falta, pregunto: "¿Qué decidiste y qué opciones había sobre la mesa antes de elegir?"
- Interesados y decisor - Requerido. Por qué los necesito: determinan si la fila queda como pending o decided. Si faltan, pregunto: "¿Quién decidió esto: tú, un cofundador, el equipo? ¿Y es definitivo o sigue abierto?"
- Derechos de decisión / RACI - Opcional. Por qué los necesito: me permiten asignar el estado correcto por defecto sin preguntar cada vez. Si no los tienes, sigo adelante con TBD y pregunto una sola vez: "¿Quién es dueño de decisiones como precios, contrataciones o estrategia de producto? Con una oración basta."
- Prioridades activas - Requerido. Por qué las necesito: etiqueto si la decisión es estructural para lo que estás impulsando. Si faltan, pregunto: "¿Cuáles son las 2 o 3 cosas que la empresa está impulsando este trimestre?"
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 · 108 lines · 75 tokens per session scan A e91f00576e2e
registrar-una-decision is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 1,673 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.