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-proposal-planninggit 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-proposal-planning)<a href="https://agentmods.dev/skills/joaoguirunas/team-os/sales-proposal-planning"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/sales-proposal-planning/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-proposal-planning"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/sales-proposal-planning.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.00092 | $0.01916 |
| Opus 5.5 | $0.00037 | $0.00766 |
| Sonnet 5.5 | $0.00018 | $0.00383 |
| Haiku 4.5 | $0.00009 | $0.00192 |
Grade A, and why
sales-proposal-planning 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Proposal Planning — a planta antes da proposta
Toda proposta que funciona tem um documento por trás que o cliente nunca vê: o planejamento interno. Ele reúne diagnóstico, oferta, roadmap, economia, governança, bastidor de negociação e a estrutura exata do que o cliente vai ler. Copy, design e números seguem a planta — quem improvisa no artefato está desfazendo o plano.
1. Os dois documentos
| Documento | Para quem | Contém | Nunca contém |
|---|---|---|---|
| Planejamento interno | Time | Tudo: diagnóstico, tese, roadmap, economia, riscos, objeções, pendências, estrutura do PDF | — |
| Proposta (PDF/deck) | Cliente | Diagnóstico na linguagem dele, oferta, roadmap com compromisso conjunto, investimento, próximo passo | Riscos, objeções, comparativo com concorrente nomeado, margem/custo interno, linguagem condicional |
Regra de ouro: proposta que lista os próprios riscos planta dúvida onde não havia. O que o cliente precisa saber sobre dependências entra como compromisso conjunto ("para o sprint 1 rodar, precisamos de…"), nunca como alerta.
Marque o topo do planejamento: Documento interno. Nunca enviar ao cliente. E marque explicitamente quais seções são bastidor.
2. As 9 seções
§1 Sumário executivo
Três parágrafos: (a) a leitura do negócio do cliente — o gargalo real, não o sintoma; (b) o que se propõe e por quê essa forma; (c) o que muda para ele. Termina com a frase de posicionamento (uma frase que o cliente repetiria). Escrito por último, lido primeiro.
§2 Diagnóstico
- Dores priorizadas, na linguagem do cliente (do intake — citação literal quando houver)
- Stack e processo atual; lacunas a fechar (o que não existe e precisa existir antes de tudo)
- Sinais de compra observados e o que cada um pede de cuidado
- Dados de mercado usados, com fonte (do research). Nunca inventar número do cliente antes do diagnóstico.
§3 Enquadramento da solução
- Qual oferta/pacote (nome exato do catálogo) e por que essa camada
- Tabela: camada → o que entrega → qual dor resolve
- Escopo IN / OUT explícito — o que fica para o backlog, o que é projeto à parte (com nota de exclusão que vai ao PDF)
- Princípios técnicos acordados na reunião (viram credibilidade no PDF)
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 · -24 tokens per session ca9d74df8e0b
- 1mo ago First seen · 91 lines · 116 tokens per session scan A c0f5373d362e
sales-proposal-planning is a skill published in the GitHub repository joaoguirunas/team-os (4 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 1,916 once invoked, about $0.0004 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
jsonl-log-analyzer
Analyze large JSONL log files using schema-aware partitioned analysis. Discovers field schema, generates tailored jq extraction recipes, and orchestrates parallel chunk analysts with synthesis. Use when processing JSONL logs exceeding context limits, performing log analytics, or investigating incident logs.
orchestration-patterns
Apply proven orchestration patterns for agent teams including parallel specialists, pipelines, swarms, research+implementation, plan approval, and multi-file refactoring. Use when choosing a team structure, designing workflows, or implementing specific coordination patterns.
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.
spawn-backends
Configure how teammate agents run including in-process, tmux, and iTerm2 backends. Use when choosing a display mode, setting up split panes, troubleshooting backend issues, or configuring teammateMode.
error-handling
Debug and recover from agent team errors including common errors, hooks for quality gates, known limitations, and recovery strategies. Use when encountering team errors, enforcing quality gates with hooks, understanding limitations, or debugging agent issues.
messaging
Send messages between agents using SendMessage including direct messages, broadcasts, shutdown requests/responses, and plan approvals. Use when communicating between agents, understanding message formats, or handling structured protocol messages.