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 ejecutar-mi-revision-operativagit 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/ejecutar-mi-revision-operativa)<a href="https://agentmods.dev/skills/gethouston/houston/ejecutar-mi-revision-operativa"><img src="https://agentmods.dev/badge/skills/gethouston/houston/ejecutar-mi-revision-operativa/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/ejecutar-mi-revision-operativa"><img src="https://agentmods.dev/badge/skills/gethouston/houston/ejecutar-mi-revision-operativa.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.00090 | $0.01624 |
| Opus 5 | $0.00045 | $0.00812 |
| Sonnet 5 | $0.00018 | $0.00325 |
| Haiku 4.5 | $0.00009 | $0.00162 |
Grade A, and why
ejecutar-mi-revision-operativa 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ejecutar mi revisión operativa
El ritual transversal de los lunes. Dos sub-revisiones detrás de una misma primitiva: normalmente quieres la revisión semanal los lunes, con el resumen de métricas conectado a ella.
Cuándo usarla
period=weekly- "revisión operativa del lunes" / "lectura semanal" / "qué pasó en mis operaciones esta semana".period=metrics-rollup- "lectura semanal de métricas" / "cómo va el negocio esta semana" / "dame los datos para la revisión del lunes".
Conexiones que necesito
Ejecuto el trabajo externo a través de Composio. Antes de correr esta habilidad 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.
- Warehouse / fuente de datos - Obligatorio para
period=metrics-rollup. Trae snapshots frescos de las métricas si los diarios están desactualizados. - Rastreador de metas (Notion, Airtable, Google Sheets) - Opcional. Permite que la revisión semanal refleje el estado actual de las metas sin un refresco manual.
Esta habilidad funciona sin ninguna conexión para la revisión semanal: se apoya en tu trabajo guardado. Solo me bloqueo en metrics-rollup si no hay un warehouse conectado.
Información que necesito
Primero leo tu contexto de operaciones. Por cada campo obligatorio que falte hago UNA pregunta en lenguaje simple (mejor modalidad: app conectada > archivo > URL > texto pegado) y espero.
- Prioridades activas - Obligatorio. Por qué las necesito: la sección de vacíos frente a prioridades depende de ellas. Si falta, pregunto: "¿Cuáles son las 2 o 3 cosas que la empresa está empujando este trimestre?"
- Ritmo operativo - Obligatorio. Por qué lo necesito: hace que "revisión del lunes" signifique lo correcto para tu semana. Si falta, pregunto: "¿Cómo es tu semana, día de revisión, días de trabajo profundo, días de reuniones?"
- Qué estás monitoreando - Obligatorio para
period=metrics-rollup. Por qué lo necesito: el resumen recorre cada métrica que observas. Si falta, pregunto: "¿Qué números miras con más atención? Lo mejor es conectar el dashboard o el warehouse donde viven." - Cadencia con inversionistas - Opcional. Por qué la necesito: permite que la revisión señale plazos próximos con inversionistas o el directorio. Si no la tienes, sigo adelante con TBD y omito la sección de plazos.
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 · 86 lines · 90 tokens per session scan A 651bc9d50c34
ejecutar-mi-revision-operativa is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 1,624 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
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.