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 calificar-mi-pipelinegit 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/calificar-mi-pipeline)<a href="https://agentmods.dev/skills/gethouston/houston/calificar-mi-pipeline"><img src="https://agentmods.dev/badge/skills/gethouston/houston/calificar-mi-pipeline/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/calificar-mi-pipeline"><img src="https://agentmods.dev/badge/skills/gethouston/houston/calificar-mi-pipeline.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.00080 | $0.02049 |
| Opus 5 | $0.00040 | $0.01025 |
| Sonnet 5 | $0.00016 | $0.00410 |
| Haiku 4.5 | $0.00008 | $0.00205 |
Grade A, and why
calificar-mi-pipeline 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Calificar mi pipeline
Una sola skill, cuatro superficies de calificación. El parámetro subject elige la rúbrica. Comparten la disciplina de "factores transparentes, sin números mágicos".
Parámetro: subject
lead: califica en bloque cada lead sin puntuar enleads.json(más cualquier vista de leads nuevos en el CRM conectado). Una pasada de todo el sistema, no de un solo lead. Devuelve una tabla clasificada.lead-fit: un solo lead con nombre: puntaje de ajuste y ángulo para presentar. Rápido, una sola fila.deal-health: cada negocio abierto endeals.json(o la vista de negocios abiertos del CRM conectado). Factores: tiempo en la etapa, qué tan completa está la calificación, qué tan reciente fue el último contacto. Devuelve GREEN / YELLOW / RED por negocio.customer-health: cada cliente actual encustomers.json. Factores: tendencia de uso del producto, puntaje de satisfacción si se capturó, volumen de tickets de soporte, señal de facturación (cercanía a una baja de plan). GREEN / YELLOW / RED, con los 2 factores principales nombrados por fila.
Si el pedido del usuario nombra el sujeto en lenguaje simple ("califica los leads", "revisión de ajuste", "salud del pipeline", "quién está en rojo"), lo infiero. Si no, hago UNA pregunta que nombre las 4 opciones.
Cuándo usarla
- Disparadores explícitos en la descripción.
- Implícito: dentro de
manage-my-crm action=route(enrutar necesita el puntaje); dentro dewrite-my-outreach stage=churn-save(una fila de customer-health en rojo dispara el intento de retención); dentro decheck-my-sales subject=pipeline(el resumen de salud usa los puntajes por negocio).
Conexiones que necesito
Todo el trabajo externo lo hago a través de Composio. Antes de ejecutar esta skill, verifico que las categorías de abajo estén conectadas. Si falta alguna, digo cuál es, te pido que la conectes desde la pestaña de Integraciones, y me detengo.
- CRM: obtengo leads, negocios abiertos, registros de clientes. Obligatorio para
lead,deal-health,customer-health. - Facturación: obtengo la señal de baja de plan o cancelación. Obligatorio para
customer-health. - Rastreo / búsqueda: enriquezco un solo lead para
lead-fit. Opcional.
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 · 107 lines · 80 tokens per session scan A 537baaf5d0cb
calificar-mi-pipeline is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 2,049 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
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…