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 marcar-una-senalgit 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/marcar-una-senal)<a href="https://agentmods.dev/skills/gethouston/houston/marcar-una-senal"><img src="https://agentmods.dev/badge/skills/gethouston/houston/marcar-una-senal/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/marcar-una-senal"><img src="https://agentmods.dev/badge/skills/gethouston/houston/marcar-una-senal.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.00096 | $0.01466 |
| Opus 5 | $0.00048 | $0.00733 |
| Sonnet 5 | $0.00019 | $0.00293 |
| Haiku 4.5 | $0.00010 | $0.00147 |
Grade A, and why
marcar-una-senal 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marcar una señal
Una skill para cada pregunta de "este hilo contiene una señal que hay que registrar". Se ramifica según signal.
Cuándo usarlo
- bug: "¿esto es un error? regístralo" / el mensaje contiene mensajes de error, trazas de pila, "antes funcionaba, ahora no", pasos de reproducción, o capturas de pantalla de la interfaz rota.
- feature-request: la conversación o el mensaje directo contiene una petición de función ("¿pueden agregar X?", "sería genial si Y").
- repeat-question: en el cron semanal, o al escanear los últimos 30 a 60 días y encontrar un grupo de preguntas entrantes semánticamente similares que llegue a ≥3 sin un artículo correspondiente.
Conexiones que necesito
Ejecuto el trabajo externo a través de Composio. Antes de que esta skill se ejecute, 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.
- Seguimiento de desarrollo (GitHub / Linear / Jira): redacto un issue para los candidatos a error confirmados. Obligatorio para
bugsi quieres que lo encadene con tu sistema de seguimiento. - Bandeja de entrada (Gmail): fuente de hilos para agrupar preguntas repetidas. Opcional si
conversations.jsonya cubre la ventana.
Si quieres que registre candidatos a error en 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. Por cada campo obligatorio que falte, te hago UNA pregunta en lenguaje sencillo (mejor modalidad: app conectada > archivo > URL > texto pegado) y espero.
- Superficie del producto: Obligatorio. Por qué la necesito: me dice qué está dentro del alcance (error real) versus fuera de alcance (de terceros). Si falta, pregunto: "¿Qué cubre realmente tu producto? Comparte una vista rápida o indícame tu página principal."
- Reglas de clasificación entre error y función: Obligatorio. Por qué la necesito: la línea entre "roto" y "faltante" determina a dónde va la señal. Si falta, pregunto: "Cuando un cliente reporta que algo no funciona, ¿qué hace que sea un error para ti, en vez de una solicitud de función?"
- Plataforma del centro de ayuda: Obligatorio para
repeat-question. Por qué la necesito: reviso la cobertura existente de la base de conocimiento antes de marcar un grupo como un hueco de documentación. Si falta, pregunto: "¿Dónde viven tus artículos de ayuda hoy? ¿Notion, Intercom, un sitio de documentación, o todavía en ningún lado?"
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 · 69 lines · 96 tokens per session scan A 699bcdcda524
marcar-una-senal is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 1,466 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.