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 revisar-mi-soportegit 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/revisar-mi-soporte)<a href="https://agentmods.dev/skills/gethouston/houston/revisar-mi-soporte"><img src="https://agentmods.dev/badge/skills/gethouston/houston/revisar-mi-soporte/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/revisar-mi-soporte"><img src="https://agentmods.dev/badge/skills/gethouston/houston/revisar-mi-soporte.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.00107 | $0.01478 |
| Opus 5 | $0.00053 | $0.00739 |
| Sonnet 5 | $0.00021 | $0.00296 |
| Haiku 4.5 | $0.00011 | $0.00148 |
Grade A, and why
revisar-mi-soporte 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Revisar mi soporte
Una sola skill para el recuento, el reporte y la revisión. Se ramifica según scope.
Cuándo usarla
- weekly - "revisión del lunes" / "reporte semanal de soporte" / "¿cómo estuvo la semana de soporte?" / rutina automática del lunes.
- help-center-digest - "resumen semanal del centro de ayuda" / "¿qué pasó en la documentación esta semana?" / rutina automática del domingo.
- account-review - "prepara la revisión de cuenta de {account}" / "esquema para el check-in con {customer}."
Conexiones que necesito
Hago el trabajo externo a través de Composio. Antes de ejecutar esta skill, 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.
- Documentos / notas (Google Docs / Notion) - publica el reporte donde tu equipo realmente lo va a leer. Opcional, si no usa markdown local como respaldo.
- Mensajería (Slack) - coloca el resumen semanal en un canal del equipo. Opcional.
- CRM (HubSpot / Attio) - trae el registro de la cuenta para el alcance account-review. Obligatorio para
account-review. - Facturación (Stripe) - trae el ingreso mensual y la fecha de renovación para el alcance account-review. Obligatorio para
account-review.
Si pides una revisión de cuenta y tu CRM no está conectado, me detengo y te pido que lo conectes.
Información que necesito
Primero leo tu contexto de soporte. Por cada campo obligatorio que falte, te hago UNA pregunta en lenguaje simple (mejor modalidad: app conectada > archivo > URL > pegar texto) y espero.
- Superficie del producto + mapa de niveles de plan - Obligatorio. Por qué lo necesito: los recuentos agrupan los elementos por dominio y nivel. Si falta, pregunto: "¿Qué planes vendes, y qué incluye más o menos cada uno?"
- Segmento de revisión de cuenta - Obligatorio para
account-review. Por qué lo necesito: no todos los clientes reciben una revisión de cuenta; necesito saber dónde está la línea. Si falta, pregunto: "¿Con qué clientes realmente haces revisiones de cuenta? ¿Solo enterprise, o cualquiera por encima de cierto ingreso mensual?" - Frecuencia de revisión - Obligatorio para
weekly. Por qué lo necesito: define la ventana del recuento. Si falta, pregunto: "¿Quieres esto semanal, cada dos semanas, o mensual?"
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 · 71 lines · 107 tokens per session scan A b1cdbf37ea1f
revisar-mi-soporte is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 107 tokens to every session and 1,478 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…