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 perfilar-a-mi-compradorgit 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/perfilar-a-mi-comprador)<a href="https://agentmods.dev/skills/gethouston/houston/perfilar-a-mi-comprador"><img src="https://agentmods.dev/badge/skills/gethouston/houston/perfilar-a-mi-comprador/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/perfilar-a-mi-comprador"><img src="https://agentmods.dev/badge/skills/gethouston/houston/perfilar-a-mi-comprador.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.00076 | $0.01407 |
| Opus 5 | $0.00038 | $0.00704 |
| Sonnet 5 | $0.00015 | $0.00281 |
| Haiku 4.5 | $0.00008 | $0.00141 |
Grade A, and why
perfilar-a-mi-comprador 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Perfilar a mi comprador
Skill más acotada que un persona de marketing. Objetivo: responder "a quién le vendemos, quién firma, quién bloquea, qué dispara la decisión", las 4 cosas que el agente y el representante necesitan para afinar la prospección y el descubrimiento.
Cuándo usarla
- "perfila el comité de compra de {segment}".
- "quién firma en {segment}" / "quién realmente nos compra".
- "arma un perfil de comprador para {segment}".
- Llamado por
set-up-my-sales-infocuando la sección del comité de compra está poco desarrollada.
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 las cuentas principales ganadas en el segmento (firmográficos, contactos, tiempo hasta el cierre). Obligatorio, a menos que prefieras que trabaje con ejemplos que tú me des.
- Redes sociales: enriquezco los perfiles del champion y del comprador económico vía LinkedIn. Opcional.
Si tu CRM no está conectado, te ofrezco trabajar con 2 o 3 ejemplos de negocios ganados que me describas directamente.
Información que necesito
Primero leo tu contexto de ventas. Por cada campo obligatorio que falte, hago UNA pregunta en lenguaje sencillo (mejor modalidad: app conectada > archivo > URL > texto pegado) y espero.
- Tu playbook de ventas: obligatorio. Por qué lo necesito: el perfil refina la sección del comité de compra que está ahí. Si falta, pregunto: "Todavía no tengo tu playbook. ¿Quieres que lo redacte primero?"
- El segmento a perfilar: obligatorio. Por qué lo necesito: el perfil es específico del segmento, no genérico. Si falta, pregunto: "¿Qué segmento debo perfilar? Industria, tamaño de empresa, geografía."
- Fuente de las cuentas: obligatorio. Por qué lo necesito: puedo tomarlas de tu CRM o trabajar con ejemplos que tú me des. Si falta, pregunto: "¿Traigo los negocios ganados en este segmento desde tu CRM conectado, o prefieres contarme 2 o 3 cuentas reales?"
- Quién firmó y quién bloqueó en negocios pasados: opcional. Por qué lo necesito: afina los patrones del comprador económico y del bloqueador. Si no lo tienes, sigo adelante con TBD en la sección de bloqueadores.
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 · 99 lines · 76 tokens per session scan A ce90a39ec7d5
perfilar-a-mi-comprador is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 1,407 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…