Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add robconery/champion/plugin install championWrote 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/commands/robconery/champion/tune-marketing)<a href="https://agentmods.dev/commands/robconery/champion/tune-marketing"><img src="https://agentmods.dev/badge/commands/robconery/champion/tune-marketing/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/commands/robconery/champion/tune-marketing"><img src="https://agentmods.dev/badge/commands/robconery/champion/tune-marketing.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.00037 | $0.00657 |
| Opus 5 | $0.00018 | $0.00329 |
| Sonnet 5 | $0.00007 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
tune-marketing 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin note: this command ships in the
championplugin, so every council agent it names is a plugin agent. When spawning any agent mentioned below, use thechampion:prefix for the agent type (e.g.champion:historian,champion:north-star,champion:viewer).Setup gate: before doing anything else, check that
~/.champion/dossier/PROFILE.mdexists. If it does not, stop immediately and tell the user, politely, that the council cannot work without knowing who it fights for: run/champion:setupfirst (a 20–30 minute interview). Do not proceed in any form until setup is complete.
tune-marketing
The marketing effort:
$ARGUMENTS
This is Optimize mode, a focused critique loop, one round, not three. The spec it optimizes against is the flywheel.
Read first (the spec)
${CLAUDE_PLUGIN_ROOT}/references/marketing-playbook.md: the whole system on one page: the flywheel, the three disciplines (one engine/asset/offer; the build is the marketing; value over scheme), and the cadence. Every fix must fit on that page or it's a scheme, not a strategy.~/.champion/dossier/VALUES.md: the user's brand line, the values every piece of marketing has to honor.
The panel (one round, spawn in parallel)
Spawn these agents on the effort:
customer: does the message land? Would I click / open / convert? Top objection, in one blunt line.researcher: what's actually working for this tactic in the wild, and what are the strongest comparable players in the user's space doing here?opportunist: is this the highest-leverage move, or busywork dressed as marketing? Where's the real return?north-star: the value-over-scheme check: is this teaching a real outcome and inviting softly, or has it drifted into selling/hype/ego?
Synthesize (you, the champion)
Score the effort against the three disciplines and the cadence. Then give the user the fixes, concrete, not vague.
Output
VERDICT: <ship / revise / kill>
FITS THE FLYWHEEL?: <which stage it serves, or where it breaks discipline>
TOP 3 FIXES:
1. <fix>
2. <fix>
3. <fix>
THE REWRITE: <if it's copy, the revised version in the user's voice (per ~/.champion/dossier/VOICE.md), else "n/a">
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 · 49 lines · 37 tokens per session scan A bdf2986a3041
tune-marketing is a command published in the GitHub repository robconery/champion (5 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 657 once invoked, about $0.0002 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.