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 ajustar-mis-reglas-de-enrutamientogit 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/ajustar-mis-reglas-de-enrutamiento)<a href="https://agentmods.dev/skills/gethouston/houston/ajustar-mis-reglas-de-enrutamiento"><img src="https://agentmods.dev/badge/skills/gethouston/houston/ajustar-mis-reglas-de-enrutamiento/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/ajustar-mis-reglas-de-enrutamiento"><img src="https://agentmods.dev/badge/skills/gethouston/houston/ajustar-mis-reglas-de-enrutamiento.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.00094 | $0.01220 |
| Opus 5 | $0.00047 | $0.00610 |
| Sonnet 5 | $0.00019 | $0.00244 |
| Haiku 4.5 | $0.00009 | $0.00122 |
Grade A, and why
ajustar-mis-reglas-de-enrutamiento 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ajustar mis reglas de enrutamiento
Cuándo usar esto
- "actualiza nuestro enrutamiento" / "arregla el enrutamiento" / "qué es error versus solicitud de función."
- "nos cambiamos a {tracker}" / "los reembolsos ahora van a {persona}" / "agrega un nivel nuevo."
- Cuando
review-my-support scope=weeklydetecta desviaciones en la clasificación.
Conexiones que necesito
Hago el trabajo externo a través de Composio. Antes de ejecutar este 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 Integraciones, y me detengo.
- Sistema de seguimiento de desarrollo (GitHub / Linear), destino nombrado para la regla de enrutamiento de errores. Obligatorio si el enrutamiento de errores termina en un sistema de seguimiento.
- Facturación (Stripe), destino nombrado para el enrutamiento de facturación. Opcional.
- Documentos / notas (Notion / Google Docs), destino nombrado para el enrutamiento del centro de ayuda o del estado. Opcional.
Si quieres que los errores fluyan hacia un sistema de seguimiento, me detengo y te pido que conectes el que realmente usas.
Información que necesito
Primero leo tu contexto de soporte. Para cada campo obligatorio que falte, hago UNA pregunta en lenguaje sencillo (mejor modalidad: app conectada > archivo > URL > texto pegado) y espero.
- Categorías de enrutamiento actuales, Obligatorio. Por qué lo necesito: reescribo a partir de tus reglas existentes, no desde cero. Si falta, pregunto: "¿En qué categorías clasificas los tickets hoy: error, cómo hacerlo, facturación, algo más?"
- Qué está cambiando, Obligatorio. Por qué lo necesito: no reescribo toda la sección si solo querías actualizar una regla. Si falta, pregunto: "¿Qué parte del enrutamiento quieres cambiar: el sistema de seguimiento, las categorías, quién aprueba los reembolsos, algo más?"
- Quién aprueba los reembolsos, Opcional. Por qué lo necesito: la regla de facturación nombra a una persona real. Si no lo tienes, sigo adelante con "por definir" y lo dejo como "el fundador aprueba."
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 · 70 lines · 94 tokens per session scan A 6f84e0e0da8a
ajustar-mis-reglas-de-enrutamiento is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 1,220 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.