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.
git 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/commands/lckx777/copy-chief-black/debate)<a href="https://agentmods.dev/commands/lckx777/copy-chief-black/debate"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/debate/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/lckx777/copy-chief-black/debate"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/debate.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.00009 | $0.01894 |
| Opus 5 | $0.00005 | $0.00947 |
| Sonnet 5 | $0.00002 | $0.00379 |
| Haiku 4.5 | $0.00001 | $0.00189 |
Grade A, and why
debate 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copy Squad Debate (N-Expert + Scoring)
Arguments: $ARGUMENTS
Step 1: Parse Arguments
Extract from $ARGUMENTS:
- experts: names separated by "vs" (case-insensitive). Minimum 2, maximum 4.
- topic: everything after "sobre" (or "about", "on", ":")
- framework: if
--frameworkflag present, extract value. Default:adversarial
Defaults:
- If only ONE expert name given (no "vs"), set expert2 =
copy-chief - If NO expert names given, set expert1 =
halbert, expert2 =schwartz - If no topic detected, ASK the user before proceeding
- If no
--framework, default toadversarial
Valid expert names (match case-insensitive, use lowercase for file): abraham, agora, bencivenga, brown, brunson, caples, carlton, chaperon, cialdini, collier, copy-chief, halbert, hopkins, hormozi, kennedy, kern, makepeace, ogilvy, powers, reeves, ry-schwartz, sabri, schwartz, sugarman, vaynerchuk
If an expert name is not in this list, report the error and list valid names. Do NOT proceed.
Framework options:
adversarial(default) — experts challenge and attack each other's positionssocratic— experts ask provocative questions to each other, drawing out deeper thinkingcollaborative— experts build on each other's ideas, seeking synthesis
Step 2: Load Voice DNA Profiles
Read ALL expert profiles:
~/.claude/copy-squad/{expert}.mdfor each expert
Extract from each file:
- Core Philosophy section (worldview and principles)
- Voice Patterns section (how they write and argue)
- Core Identity line from the header
These define HOW each expert speaks during the debate. Each expert MUST stay in character throughout all rounds.
Step 3: Detect Active Offer (Optional)
Check if the current working directory contains an active offer:
find ~/copywriting-ecosystem -maxdepth 4 -name "CONTEXT.md" -newer ~/copywriting-ecosystem/.git/HEAD 2>/dev/null | head -3
If an active offer is detected, note its path for saving output later. If not, output will go to chat only.
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 · 233 lines · 9 tokens per session scan A 2c73fda7823e
debate is a command published in the GitHub repository lckx777/copy-chief-black (5 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 1,894 once invoked, about $0.0000 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.