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 brand-trackinggit 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/brand-tracking)<a href="https://agentmods.dev/skills/joaoguirunas/team-os/brand-tracking"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/brand-tracking/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/brand-tracking"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/brand-tracking.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.01344 |
| Opus 5.5 | $0.00037 | $0.00538 |
| Sonnet 5.5 | $0.00018 | $0.00269 |
| Haiku 4.5 | $0.00009 | $0.00134 |
Grade A, and why
brand-tracking 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Tracking — o antes, o depois, e nenhum número sem dono
Reposicionamento sem linha de base é fé. Comparação com método diferente é ilusão. Número sem ficha é boato com casas decimais. Este método existe para que, seis meses depois, alguém consiga dizer o que mudou, com que confiança e o que não dá para atribuir — e para que nenhum número apareça em manifesto, brandbook ou deck sem ter passado pela ficha.
1. Princípios
- Baseline antes de qualquer aplicação nova sair. Se não der tempo, o usuário decide por escrito sabendo que o lançamento sai sem prova de resultado.
- Mesmo método no antes e no depois — métrica, fonte, janela, população. Mudou o método, nova série começa do zero e o relatório diz isso.
- Toda métrica tem definição operacional (como exatamente se calcula), fonte, cadência, dono e limitações. Proxy é declarado como proxy.
- Todo número tem
#idna ficha, com status ABERTO/FECHADO. Só FECHADO sai em deliverable. - n baixo é declarado. Abaixo de ~100 respostas, "não generalizável" vai junto do número.
2. O scorecard
2.1 Funil de marca (público prioritário da plataforma)
| Métrica | Definição operacional | Fonte típica | Limitação típica |
|---|---|---|---|
| Awareness espontânea | % que cita a marca ao pensar na categoria (pergunta aberta) | survey própria | amostra, viés de quem responde |
| Awareness estimulada | % que reconhece a marca numa lista | survey própria | lista enviesa |
| Consideração | % que consideraria a marca na próxima decisão | survey | intenção ≠ ação |
| Preferência | % que escolheria a marca entre as alternativas mapeadas | survey | idem |
| Recomendação | NPS ou % que recomendou nos últimos N meses | survey / CRM | NPS varia com o momento |
2.2 Atributos de percepção
Um por traço/promessa da plataforma (§3): "% que associa {atributo} à marca" — e aos 2–3 concorrentes do território, para ler distância. Atributo da plataforma que não é mensurável com as fontes disponíveis: avisar a strategist por escrito e propor proxy declarado.
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 · -39 tokens per session 53bbeeb0b78b
- 29d ago First seen · 72 lines · 131 tokens per session scan A c84a1ff2123d
brand-tracking 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,344 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-17.
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.