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-copygit 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-copy)<a href="https://agentmods.dev/skills/joaoguirunas/team-os/sales-proposal-copy"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/sales-proposal-copy/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-copy"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/sales-proposal-copy.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.00088 | $0.01616 |
| Opus 5.5 | $0.00035 | $0.00646 |
| Sonnet 5.5 | $0.00018 | $0.00323 |
| Haiku 4.5 | $0.00009 | $0.00162 |
Grade A, and why
sales-proposal-copy 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Proposal Copy — a proposta afirma
Texto de proposta não é texto de site nem de anúncio: o leitor já conversou com você, tem uma dor nomeada e vai decidir com base no que está escrito. Cada frase ou aumenta a confiança ou planta uma dúvida. Esta skill dá o método e a régua — um conjunto de regras verificáveis que a redatora aplica antes de entregar e o QA aplica antes de aprovar.
1. Voz
- Declarativa, presente do indicativo. "O sistema entra no ar em 14 dias." Não "esperamos colocar", "pretendemos", "deve entrar".
- Sujeito é a empresa ou o cliente — nunca abstrações ("a solução permitirá"). "Nós configuramos; vocês nomeiam um dono interno."
- Frases curtas. Uma ideia por frase, um argumento por página.
- Especificidade sobre adjetivo. "Resposta em segundos" > "resposta rápida". "3 landing pages com manutenção" > "páginas completas".
- Linguagem do cliente nas páginas de diagnóstico — as palavras que ele usou na reunião (do intake), não as suas.
- Tom, termos fixos, emoji, maiúsculas, pontuação: conforme a nota de marca do projeto (
project/brand.md). Sem nota de marca, pergunte — não improvise.
2. O arco em três aberturas
| Abertura | Pergunta que responde | Páginas típicas |
|---|---|---|
| I — O ponto de partida | Vocês me entenderam? | O que ouvimos (dores, literal) · onde a receita/tempo vaza (com dados e fonte) · a oportunidade |
| II — O que entregamos | Como isso resolve? | A oferta em uma imagem · o método/módulos · o roadmap por marcos · o que você passa a enxergar |
| III — Como começamos | O que eu faço agora? | Governança e "para o marco 1 rodar" · investimento (o que inclui/exclui/termos) · próximo passo e aceite |
Cada página tem título-asserção (afirma algo: "Onde a receita vaza", não "Diagnóstico"), corpo que prova a asserção e uma ponte para a próxima. A frase de posicionamento aparece no máximo duas vezes: abertura e fecho.
3. Regras do que vai e do que não vai
Vai
- Dores na linguagem do cliente
- Oferta com nomes exatos do catálogo
- Roadmap com marcos e o que fica pronto em cada um
- Compromisso conjunto: tabela "o que entregamos / o que precisamos de vocês" — é a única forma permitida de falar de dependência
- Investimento, inclusões, exclusões, termos, próximo passo
- Números com origem na ficha da financeira (
#id) e dados de mercado com fonte
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 · -2 tokens per session 0cbed9950e11
- 1mo ago First seen · 97 lines · 90 tokens per session scan A 31f9279afc25
sales-proposal-copy is a skill published in the GitHub repository joaoguirunas/team-os (4 stars, last pushed 2d ago), licensed MIT. It adds 88 tokens to every session and 1,616 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.