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 planear-un-onboardinggit 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/planear-un-onboarding)<a href="https://agentmods.dev/skills/gethouston/houston/planear-un-onboarding"><img src="https://agentmods.dev/badge/skills/gethouston/houston/planear-un-onboarding/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/planear-un-onboarding"><img src="https://agentmods.dev/badge/skills/gethouston/houston/planear-un-onboarding.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.00084 | $0.01166 |
| Opus 5 | $0.00042 | $0.00583 |
| Sonnet 5 | $0.00017 | $0.00233 |
| Haiku 4.5 | $0.00008 | $0.00117 |
Grade A, and why
planear-un-onboarding 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planear un onboarding
Primer artefacto después del cierre. Deja explícita la métrica de éxito para que el puntaje de salud sea honesto frente a ella el año siguiente.
Cuándo usarla
- "planea el onboarding de {customer}".
- "plan de kickoff para {customer}".
- Disparador posterior al cierre cuando el estado del plan de cierre cambia a
closed-won.
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: leo el registro del negocio cerrado (cuenta, contactos, monto, plazo). Opcional pero recomendado.
- Calendario: agendo el kickoff una vez que lo apruebes. Opcional.
Puedo ejecutar esta skill solo con tu plan de cierre y tu propuesta existentes, así que ninguna conexión es obligatoria.
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: contiene tu forma estándar de definir la métrica de éxito y el ritmo de tiempo hasta el valor. Si falta, pregunto: "Todavía no tengo tu playbook. ¿Quieres que lo redacte ahora?"
- Para qué cliente es: obligatorio. Por qué lo necesito: leo el plan de cierre y la propuesta de ese negocio para extraer el problema que declararon. Si falta, pregunto: "¿Para qué cliente es este onboarding?"
- Su métrica de éxito en sus propias palabras: obligatorio. Por qué lo necesito: el plan se ancla a la métrica que le importa a él, no a la nuestra. Si falta, pregunto: "¿Cómo va a saber el cliente que esto funcionó? ¿Qué dijo que se vería como éxito?"
- Fecha del kickoff: opcional. Por qué lo necesito: ancla la línea de tiempo de 90 días. Si no la tienes, sigo adelante con TBD y propongo una fecha basada en el inicio del contrato.
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 · 86 lines · 84 tokens per session scan A 24fbd38d2b23
planear-un-onboarding is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 1,166 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.