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 revisar-mis-ventasgit 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/revisar-mis-ventas)<a href="https://agentmods.dev/skills/gethouston/houston/revisar-mis-ventas"><img src="https://agentmods.dev/badge/skills/gethouston/houston/revisar-mis-ventas/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/revisar-mis-ventas"><img src="https://agentmods.dev/badge/skills/gethouston/houston/revisar-mis-ventas.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.00099 | $0.02096 |
| Opus 5 | $0.00049 | $0.01048 |
| Sonnet 5 | $0.00020 | $0.00419 |
| Haiku 4.5 | $0.00010 | $0.00210 |
Grade A, and why
revisar-mis-ventas 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Revisar mis ventas
Una skill, cinco superficies de análisis. El parámetro subject elige el alcance. Comparten la disciplina de "siguientes pasos por encima de dashboards".
Parámetro: subject
sales-health- lectura del lunes. Junto todas las salidas de skills de la última semana desdeoutputs.json. Agrupo por dominio (Playbook, Outbound, Inbound, Meetings, CRM, Retention). Marco trabajo estancado + seguimientos perdidos + retrasos.call-insights- síntesis cruzando N llamadas: lenguaje de dolor, frecuencia de objeciones, patrones de ganados/perdidos, con sugerencias concretas de ajustes al playbook.win-loss- agrupo los negocios ganados y perdidos por razón. Encuentro 3 patrones que se repiten. Propongo ajustes al playbook (afinar el cliente ideal, agregar entradas al manual de objeciones, ajustes de precio).discovery-call- análisis profundo de una sola llamada: talk-ratio (objetivo 40% vendedor / 60% prospecto), puntaje de dolor, brechas de calificación frente al marco del playbook, riesgos / oportunidades, borrador de seguimiento.pipeline- foto por etapa + ingreso anual + velocidad de negocios + la transición que más se filtra. Ancla el forecast semanal.
Si el usuario nombra el sujeto en lenguaje simple ("revisión de ventas", "analiza mis llamadas", "ganados y perdidos", "cómo salió esa llamada", "revisión de pipeline") lo infiero. Si no, hago UNA pregunta nombrando las 5 opciones.
Cuándo usarlo
- Disparadores explícitos en la descripción.
- Implícito:
capture-my-call-notesencadena acheck-my-sales subject=discovery-callpara completar el ciclo post-llamada. La rutina semanal "revisión de ventas del lunes" disparasubject=sales-health.run-my-forecastencadena asubject=pipelinepara la capa narrativa.
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.
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 · 79 lines · 99 tokens per session scan A 24350180effe
revisar-mis-ventas is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 2,096 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…