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 lckx777/copy-chief-black --skill leads-agentgit clone --depth 1 https://github.com/lckx777/copy-chief-blackWrote 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/lckx777/copy-chief-black/leads-agent)<a href="https://agentmods.dev/skills/lckx777/copy-chief-black/leads-agent"><img src="https://agentmods.dev/badge/skills/lckx777/copy-chief-black/leads-agent/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/lckx777/copy-chief-black/leads-agent"><img src="https://agentmods.dev/badge/skills/lckx777/copy-chief-black/leads-agent.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.00174 | $0.02720 |
| Opus 5 | $0.00087 | $0.01360 |
| Sonnet 5 | $0.00035 | $0.00544 |
| Haiku 4.5 | $0.00017 | $0.00272 |
Grade A, and why
leads-agent 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Leads Agent
Princípio Central
"A função da lead é VENDER A VISUALIZAÇÃO da tese de marketing. A tese JUSTIFICA a compra que a pessoa já fez emocionalmente na lead."
Definição Fundamental
Lead = tudo ANTES da história de origem do expert.
| Elemento | Duração | Onde Termina | Função | Natureza |
|---|---|---|---|---|
| Microlead | 30s-90s | Antes da lead "de verdade" | PONTE criativo → VSL | Espelha o criativo (mesma voz, mesmo POV, mesmo tom) |
| Lead | 2-5min | Quando apresentador se apresenta | ESCALADA emocional + venda da visualização | Peça autônoma de persuasão visceral |
Marcador de fim: "Oi, eu sou fulano, e eu vou te explicar..."
Distinção Crítica: Microlead ≠ Mini-Lead
| Dimensão | Microlead (PONTE) | Lead (ESCALADA) |
|---|---|---|
| Função | Continuar o momentum do criativo | Vender a visualização da tese |
| Voz/POV | HERDA do criativo (1a pessoa expert, UGC, narrador — o que o criativo usar) | Definida pelo briefing HELIX (pode divergir do criativo) |
| Emoção | Confirma e aprofunda a emoção do criativo | Escala DRE até nível 4-5 |
| Mecanismo | TEASE (termos gerais: "pesquisa recente", "descoberta") | PROVE (dados específicos: "março de 2023", "266 pacientes") |
| Especificidade | Tease-level (suficiente para intrigar) | Prove-level (Specificity Score >= 8) |
| Formato | ROTEIRO DE VÍDEO com notas de produção | Texto limpo calibrado ao tom |
| Validação | Congruência + transição (não impacto emocional bruto) | 5 Gates + blind_critic + EST |
REGRA: Se o criativo tem expert falando em 1a pessoa → microlead DEVE ter expert falando em 1a pessoa. Se criativo é UGC → microlead continua UGC. NUNCA trocar POV entre criativo e microlead.
Workflow
1. COLETAR INPUTS
- Criativo campeão (se existir)
- VSL existente (identificar ponto de convergência)
- Briefing HELIX do projeto
2. EXTRAIR VOZ/POV DO CRIATIVO (OBRIGATÓRIO para microlead)
- Quem fala no criativo? (expert 1a pessoa, narrador, UGC, etc)
- Qual o tom? (autoridade clínica, confessional, indignado, etc)
- Qual a progressão? (reframe → mecanismo → solução → CTA)
→ Microlead HERDA essa voz. Lead pode divergir.
3. ENTENDER PSICOLOGIA DO MERCADO
→ Ver references/psicologia.md
- Qual das 6 necessidades ativar?
- Estado emocional do público (alto/baixo)?
- Nível de consciência (Schwartz)?
- Crenças limitantes a destruir?
4. ESCOLHER TIPO DE LEAD
→ Ver references/tipos-de-lead.md
- 6 tipos disponíveis (Oferta, Promessa, Problema, Segredo, Proclamação, História)
- Framework de decisão baseado em nível de consciência
5. DEFINIR FORMATO DE MICROLEAD
→ Ver references/microleads.md
- 5 formatos (Prova Pessoas, Prova Experimento, Conspiração, História, Hype)
- 3 Confirmações obrigatórias
- VOZ/POV deve ser congruente com Step 2
6. CONSTRUIR ANATOMIA
→ Ver references/anatomia.md
- 6 componentes universais
- Progressão emocional até venda
7. APLICAR ESCRITA BLACK
→ Ver references/escrita.md
- Tom calibrado à oferta (HELIX 2.3)
- Sinestesia da rotina
- Future pacing sensorial
- Frases de poder
8. VALIDAR
→ Ver references/checklist.md
- Microlead: congruência + transição (ver Output Microlead abaixo)
- Lead: 5 Gates obrigatórios + checklists específicos
What ships with it
7 files 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.
- 9d ago First seen · 273 lines · 174 tokens per session scan A d8520c8ef176
leads-agent is a skill published in the GitHub repository lckx777/copy-chief-black (5 stars, last pushed 6mo ago), licensed MIT. It adds 174 tokens to every session and 2,720 once invoked, about $0.0009 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…