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 joaoguirunas/team-os --skill sales-discovery-intakegit clone --depth 1 https://github.com/joaoguirunas/team-osWrote 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/joaoguirunas/team-os/sales-discovery-intake)<a href="https://agentmods.dev/skills/joaoguirunas/team-os/sales-discovery-intake"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/sales-discovery-intake/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/joaoguirunas/team-os/sales-discovery-intake"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/sales-discovery-intake.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00082 | $0.01372 |
| Opus 5.5 | $0.00033 | $0.00549 |
| Sonnet 5.5 | $0.00016 | $0.00274 |
| Haiku 4.5 | $0.00008 | $0.00137 |
Grade A, and why
sales-discovery-intake 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 20d 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.
Sales Discovery Intake — da reunião à ficha
Uma proposta boa começa com um diagnóstico que o cliente reconhece como seu. Esta skill converte material bruto de discovery em uma ficha de intake que o planejador, a estrategista e a financeira consomem sem voltar à gravação.
Princípio único: o que o cliente disse é dado; o que você deduziu é hipótese; o que falta é pergunta. Os três nunca se misturam na ficha.
1. Insumos aceitos
| Insumo | Como tratar |
|---|---|
| Transcrição (call, reunião) | Fonte primária. Citações literais com marcador de tempo quando houver |
| Resumo escrito por alguém do time | Fonte secundária — marcar [resumo de {autor}]; não vira citação |
| E-mails, mensagens | Literal, com data |
| Screenshots de chamada / anotações | Transcrever o que está legível; o resto é [ILEGÍVEL] |
| Site, redes, materiais públicos do cliente | Pesquisa, não intake — vai para o research report |
Nunca inferir o que não está no material. Se duas fontes divergem, registre ambas e marque [CONFIRMAR COM O CLIENTE].
2. O que extrair — em ordem
2.1 Dores, priorizadas e na linguagem do cliente
| # | Dor | Como o cliente descreveu (literal) | Impacto que ele percebe | Prioridade |
|---|
Regras:
- Prioridade = Crítica (ele abriu a reunião com isso / repetiu / tem número) · Alta (mencionou com detalhe) · Média (surgiu de passagem)
- A coluna literal é obrigatória para dores Críticas — é ela que vira a página "O que ouvimos" da proposta
- Dor política (impacto em pessoas, cargos, fornecedores atuais) recebe a tag
sensível— precisa de tratamento cuidadoso no planejamento
2.2 Stack e processo atual
Ferramentas, planilhas, pessoas, integrações que não se falam, o que é manual, o que já foi tentado. Quem opera hoje. Custos declarados de ferramentas.
2.3 Sinais de compra
Perguntas que revelam que o cliente já se projeta usando a solução ("como fica a comissão de venda recuperada?", "dá pra virar um produto depois?", "e o meu time?"). Cada sinal vira argumento ou cuidado no planejamento.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 20d ago Changed · -8 tokens per session 70ce2374cdfa
- 1mo ago First seen · 86 lines · 90 tokens per session scan A 561204478ba5
sales-discovery-intake is a skill published in the GitHub repository joaoguirunas/team-os (4 stars, last pushed 2d ago), licensed MIT. It adds 82 tokens to every session and 1,372 once invoked, about $0.0003 per session on Opus 5.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-16.
Other skills, from other repositories
task-system
Manage shared task lists for agent teams including creating tasks, setting dependencies, claiming work, and tracking progress. Use when creating work items, building task pipelines, coordinating task ownership, or managing task dependencies.
brain-standup
Launch the standup meeting UI — a cinematic visualization of each agent role's status report. Trigger: /brain-standup.
notion
Search, read, create, and update Notion pages via the Notion MCP.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
day-one-patch
Day-one launch patch — focused fix for known issues found after gold master. Mini-sprint with QA gate and rollback.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.