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 buscar-leadsgit 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/buscar-leads)<a href="https://agentmods.dev/skills/gethouston/houston/buscar-leads"><img src="https://agentmods.dev/badge/skills/gethouston/houston/buscar-leads/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/buscar-leads"><img src="https://agentmods.dev/badge/skills/gethouston/houston/buscar-leads.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.00101 | $0.01610 |
| Opus 5 | $0.00051 | $0.00805 |
| Sonnet 5 | $0.00020 | $0.00322 |
| Haiku 4.5 | $0.00010 | $0.00161 |
Grade A, and why
buscar-leads 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Buscar leads
Saco leads nuevos en un segmento.
Cuándo usarlo
- "búscame {N} leads en {segmento}".
- "muéstrame leads a los que pueda escribirles esta semana".
- "arma leads de {post de LinkedIn / subreddit / evento}".
- Programado: rutina semanal de prospección.
Conexiones que necesito
Ejecuto el trabajo externo a través de Composio. Antes de correr esta skill reviso 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.
- CRM - para expandir a partir de parecidos a tus cuentas ganadas. Obligatorio si eliges esa fuente.
- Redes sociales - para traer a quienes comentaron en un post o hilo de LinkedIn. Obligatorio si eliges esa fuente.
- Búsqueda / investigación - para traer señales de rondas de inversión recientes o contrataciones recientes. Obligatorio si eliges esa fuente.
- Scraping - para leer una página de resultados de Google Maps o un subreddit. Obligatorio si eliges esa fuente.
Si ninguna de las categorías de fuente está conectada, me detengo y te pido conectar al menos una (el CRM es el mejor lugar para empezar porque los parecidos a tus ganados convierten mejor).
Información que necesito
Primero leo tu contexto de ventas. Por cada campo obligatorio que falte, hago UNA pregunta en lenguaje simple (mejor modalidad: app conectada > archivo > URL > pegar texto) y espero.
- Tu playbook de ventas - Obligatorio. Por qué lo necesito: necesito tu perfil de cliente ideal y tus descalificadores para puntuar candidatos con honestidad. Si falta, pregunto: "Todavía no tengo tu playbook, ¿quieres que lo redacte ahora?"
- El segmento en el que quieres leads - Obligatorio. Por qué lo necesito: "leads" es demasiado amplio para filtrar contra tu perfil de cliente ideal. Si falta, pregunto: "¿De qué segmento debería traerlos, industria, tamaño de empresa, rol, geografía?"
- Cuántos leads quieres - Obligatorio. Por qué lo necesito: limita la búsqueda y el archivo. Si falta, pregunto: "¿Cuántos leads quieres que te muestre, 10, 20, 50?"
- De dónde sacarlos - Obligatorio. Por qué lo necesito: cada fuente usa una herramienta conectada distinta. Si falta, pregunto: "¿Expando parecidos desde tu CRM, traigo a los que comentaron en un post de LinkedIn, reviso un feed de rondas de inversión recientes, hago scraping de una zona en Google Maps, o saco un hilo de un subreddit?"
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 · 112 lines · 101 tokens per session scan A 216fc53571a2
buscar-leads is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 101 tokens to every session and 1,610 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…