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 configurar-o-monitoramentogit 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/configurar-o-monitoramento)<a href="https://agentmods.dev/skills/gethouston/houston/configurar-o-monitoramento"><img src="https://agentmods.dev/badge/skills/gethouston/houston/configurar-o-monitoramento/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/configurar-o-monitoramento"><img src="https://agentmods.dev/badge/skills/gethouston/houston/configurar-o-monitoramento.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.00085 | $0.03165 |
| Opus 5 | $0.00043 | $0.01582 |
| Sonnet 5 | $0.00017 | $0.00633 |
| Haiku 4.5 | $0.00009 | $0.00316 |
Grade A, and why
configurar-o-monitoramento 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configurar o Monitoramento
Uma skill para o monitoramento que você precisa. O parâmetro scope escolhe o formato: uma definição de métrica única com capturas diárias, ou uma especificação completa de dashboard (seções + visualizações + cadência + SQL por visualização). As duas escrevem apenas SQL somente leitura e se baseiam no seu contexto operacional.
Parâmetro: scope
metric- define uma única métrica, escreve o SQL somente leitura contra o seu warehouse, captura o valor atual emmetrics-daily.json, adiciona a definição emconfig/metrics.json, e a registra na cadência escolhida. Saída:config/metrics.jsonatualizado +metrics-daily.json+queries/{metric-slug}/.dashboard- propõe de 2 a 4 seções, visualizações por seção, cadência, e o SQL somente leitura por trás de cada visualização. Apenas especificação - você ou sua ferramenta de BI renderiza. Saída:config/dashboards.json(adicionado ou atualizado por id).
O usuário nomeia o scope em linguagem simples ("acompanhar receita mensal", "monitorar usuários ativos semanais", "especificar um dashboard de crescimento", "quero ver retenção regularmente") -> eu infiro. Ambíguo -> pergunto UMA pergunta nomeando as duas opções.
Quando usar
metric:
- "comece a acompanhar {X}" / "adicione {métrica} ao dashboard" / "monitore {métrica chave}"
- Uma métrica nomeada pelo usuário em
onboard-metem um placeholder vazio emsqlSnippet, o usuário invoca esta skill para construir a definição real.
dashboard:
- "especifique um dashboard para {X}"
- "quero ver {grupo de métricas} regularmente"
- "construa um dashboard para o time de {crescimento / retenção / churn / receita}"
Conexões que eu preciso
Eu executo trabalho externo através do Composio. Antes desta skill 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 (Postgres, BigQuery, Snowflake, Redshift) - Obrigatório para
scope=metric(eu não consigo capturar uma métrica sem uma fonte para ler). Opcional parascope=dashboard(me permite escrever trechos de SQL que rodam no seu schema real; sem isso eu deixo placeholders parametrizados). - Cobrança (Stripe) - Opcional para
scope=metric. Me permite conectar métricas de receita diretamente da cobrança em vez de inferir a partir do warehouse.
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 · 174 lines · 85 tokens per session scan A b3919faf71c7
configurar-o-monitoramento is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 3,165 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.