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 executar-minha-revisao-operacionalgit 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/executar-minha-revisao-operacional)<a href="https://agentmods.dev/skills/gethouston/houston/executar-minha-revisao-operacional"><img src="https://agentmods.dev/badge/skills/gethouston/houston/executar-minha-revisao-operacional/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/executar-minha-revisao-operacional"><img src="https://agentmods.dev/badge/skills/gethouston/houston/executar-minha-revisao-operacional.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.01632 |
| Opus 5 | $0.00046 | $0.00816 |
| Sonnet 5 | $0.00019 | $0.00326 |
| Haiku 4.5 | $0.00009 | $0.00163 |
Grade A, and why
executar-minha-revisao-operacional 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executar minha revisão operacional
Ritual transversal de segunda-feira. Duas sub-revisões atrás de uma única primitiva, normalmente você quer a revisão semanal nas segundas, com o resumo de métricas alimentando ela.
Quando usar
period=weekly- "revisão operacional de segunda" / "resumo semanal" / "o que aconteceu na minha operação essa semana".period=metrics-rollup- "resumo semanal de métricas" / "como o negócio está indo essa semana" / "me dá os dados para a revisão de segunda".
Conexões que eu preciso
Eu executo trabalho externo através do Composio. Antes desta habilidade rodar, eu verifico se as categorias abaixo estão conectadas. Faltando → eu nomeio a categoria, peço para você conectar na aba Integrações, e paro.
- Warehouse / fonte de dados - Obrigatório para
period=metrics-rollup. Extrai retratos atualizados das métricas se os diários estiverem desatualizados. - Rastreador de metas (Notion, Airtable, Google Sheets) - Opcional. Permite que a revisão semanal reflita o estado atual das metas sem atualização manual.
Esta habilidade funciona sem nenhuma conexão para a revisão semanal, ela se apoia no seu trabalho salvo. Eu só bloqueio no metrics-rollup se nenhum warehouse estiver conectado.
Informações que eu preciso
Eu leio o seu contexto operacional primeiro. Para cada campo obrigatório que estiver faltando, eu faço UMA pergunta em linguagem simples (melhor modalidade: app conectado > arquivo enviado > URL > colar) e espero.
- Prioridades ativas - Obrigatório. Por que eu preciso: a seção de lacunas versus prioridades depende delas. Se estiver faltando, eu pergunto: "Quais são as 2 a 3 coisas que a empresa está priorizando neste trimestre?"
- Ritmo operacional - Obrigatório. Por que eu preciso: faz "revisão de segunda" significar a coisa certa para a sua semana. Se estiver faltando, eu pergunto: "Como é a sua semana, dia de revisão, dias de trabalho focado, dias de reunião?"
- O que você está monitorando - Obrigatório para
period=metrics-rollup. Por que eu preciso: o resumo percorre toda métrica que você acompanha. Se estiver faltando, eu pergunto: "Quais números você acompanha mais de perto? O melhor é conectar o painel ou warehouse onde eles vivem." - Ritmo com investidores - Opcional. Por que eu preciso: permite que a revisão sinalize prazos de investidores ou do conselho se aproximando. Se você não tiver isso, eu sigo em frente com dado pendente e pulo a seção de prazos.
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 · 86 lines · 93 tokens per session scan A 7cdfc60cda40
executar-minha-revisao-operacional 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,632 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.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.
remove
Remove a deployed framework or addon from the current workspace.