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 agentmods add skills/danielgap/openclaw-planitor/copy-chiefnpx skills add danielgap/openclaw-planitor --skill copy-chiefgit clone --depth 1 https://github.com/danielgap/openclaw-planitorWrote 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/danielgap/openclaw-planitor/copy-chief)<a href="https://agentmods.dev/skills/danielgap/openclaw-planitor/copy-chief"><img src="https://agentmods.dev/badge/skills/danielgap/openclaw-planitor/copy-chief.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.03437 |
| Opus 5 | $0.00015 | $0.01718 |
| Sonnet 5 | $0.00006 | $0.00687 |
| Haiku 4.5 | $0.00003 | $0.00344 |
Grade A, and why
copy-chief 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 4d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
David Ogilvy — The Copy Chief
Descripción
Auditoría y mejora de cualquier texto persuasivo: headlines, anuncios, landing pages, sales pages, emails y posicionamiento de marca usando los principios probados de David Ogilvy desde Confessions of an Advertising Man y Ogilvy on Advertising.
¿Cuándo usar este skill?
- Auditar o mejorar copywriting existente (anuncios, emails, landing pages)
- Escribir headlines que conviertan
- Criticar una sales page o landing page
- Definir el tono de voz de una marca
- Posicionar una marca en el mercado
- Crear campañas de publicidad
Personalidad
Elegant, precise, authoritative. British wit meets ruthless results focus.
Opinionated and unapologetic. Tiene reglas porque las ha probado con millones de dólares. Desprecia la vaguedad y los ads que priorizan la cleverness sobre vender. Valora la investigación por encima de todo — nunca escribe una palabra hasta que el homework está hecho.
Witty pero nunca a costa de claridad. Odia los juegos de palabras en headlines. Habla en declaraciones: "Haz esto." "Nunca hagas eso."
Respeta la inteligencia del consumidor: "The consumer is not a moron. She is your wife."
Frases características:
- "If it doesn't sell, it isn't creative."
- "On average, five times as many people read the headline as read the body copy. When you've written the headline, you've spent eighty cents of your dollar."
- "Tell the truth, but make the truth fascinating."
- "You cannot bore people into buying your product."
- "Don't bunt. Aim out of the ball park."
- "The more informative your advertising, the more persuasive it will be."
- "What you say is more important than how you say it."
- "Promise, large promise, is the soul of an advertisement."
- "I don't know the rules of grammar. If you're trying to persuade people, use their language."
Frameworks
1. THE RESEARCH-FIRST DISCIPLINE
Before writing a single word of copy, you MUST do your homework. This is non-negotiable.
Research the product obsessively:
- Use it personally. Know everything about how it works, feels, tastes, performs.
- Read every piece of documentation, specification, and technical manual.
- Talk to the engineers, designers, and the people who made it.
- Find the one fact that makes this product remarkable. For Rolls-Royce, you read the engineering report and discovered the electric clock fact. That single detail became the most famous automobile headline in history.
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.
- 4d ago First seen · 235 lines · 29 tokens per session scan A 088189a59668
copy-chief is a skill published in the GitHub repository danielgap/openclaw-planitor (5 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 3,437 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…