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 armar-una-battlecardgit 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/armar-una-battlecard)<a href="https://agentmods.dev/skills/gethouston/houston/armar-una-battlecard"><img src="https://agentmods.dev/badge/skills/gethouston/houston/armar-una-battlecard/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/armar-una-battlecard"><img src="https://agentmods.dev/badge/skills/gethouston/houston/armar-una-battlecard.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.00093 | $0.01657 |
| Opus 5 | $0.00046 | $0.00829 |
| Sonnet 5 | $0.00019 | $0.00331 |
| Haiku 4.5 | $0.00009 | $0.00166 |
Grade A, and why
armar-una-battlecard 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Armar una battlecard
NO es una hoja de comparación genérica. Una tarjeta por prospecto, anclada en lo que le importa a ESE prospecto.
Cuándo usarlo
- Usuario: "nos están evaluando contra {competidor}" / "arma la battlecard del negocio Acme vs {competidor}" / "cómo le gano a {competidor} en este caso".
- Llamada en línea por
write-my-outreachocheck-my-sales subject=discovery-callcuando se nombra un competidor en la transcripció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.
- Scraping - para leer la página de marketing del competidor, sus precios, y reseñas recientes. Obligatorio.
- Búsqueda / investigación - para traer reseñas recientes, hilos de foros, y debilidades conocidas. Obligatorio.
- CRM - para leer el contexto del negocio del prospecto y anclar la tarjeta. Opcional.
Si ninguna de las categorías obligatorias está conectada, me detengo y te pido conectar Firecrawl primero, porque la tarjeta depende de una lectura fresca del competidor.
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: de ahí saco los diferenciadores, las cuentas ancla, y los puntos de prueba. Si falta, pregunto: "Todavía no tengo tu playbook, ¿quieres que lo redacte ahora?"
- Nombre del prospecto y nombre del competidor - Obligatorio. Por qué lo necesito: la tarjeta se ancla en un negocio específico frente a un competidor específico, no es una hoja genérica. Si falta, pregunto: "¿Para qué negocio es esto, y con qué competidor nos están comparando?"
- Tu diferenciador principal y tu mayor debilidad frente a este competidor - Obligatorio. Por qué lo necesito: la tarjeta solo es honesta si sé cómo realmente ganas y pierdes. Si falta, pregunto: "¿Cuál es, con honestidad, tu principal diferenciador frente a este competidor, y tu mayor debilidad?"
- Clientes ancla ganados que se parezcan al prospecto - Opcional. Por qué lo necesito: los puntos de prueba pegan más fuerte cuando calzan con el perfil del prospecto. Si no lo tienes, sigo con TBD.
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 · 66 lines · 93 tokens per session scan A c95151b2370a
armar-una-battlecard is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 1,657 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…