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/production-brief)<a href="https://agentmods.dev/commands/lckx777/copy-chief-black/production-brief"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/production-brief/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/production-brief"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/production-brief.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.00014 | $0.01491 |
| Opus 5 | $0.00007 | $0.00745 |
| Sonnet 5 | $0.00003 | $0.00298 |
| Haiku 4.5 | $0.00001 | $0.00149 |
Grade A, and why
production-brief 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 11d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/production-brief — Offer Health Report
Input: $ARGUMENTS
Two modes:
- No argument — Dashboard showing all offers with phase and gate status
- With offer name — Detailed health report + generate consolidated production brief for that offer
MODE A: All Offers Dashboard (no argument)
When $ARGUMENTS is empty, scan all offers and display a summary table.
Step 1: Discover All Offers
find ~/copywriting-ecosystem -name "helix-state.yaml" -type f 2>/dev/null
Step 2: For Each Offer, Read State Files
helix-state.yaml— current phase, gates, HELIX phases completedmecanismo-unico.yaml— mechanism stateproject_state.yaml— last activity, next action
Step 3: Display Summary Table
OFFERS HEALTH REPORT — [date]
| Offer | Niche | Phase | Research | Briefing | Mechanism | Production |
|--------------------|-------------|------------|----------|----------|------------|---------------|
| florayla | saude | Prod Ready | PASSED | PASSED | APPROVED | NOT_STARTED |
| neuvelys | saude | Research | PENDING | — | UNDEFINED | — |
| quimica-amarracao | relacion. | Production | PASSED | PASSED | VALIDATED | IN_PROGRESS |
Active: 3 | Standby: 6
BLOCKED OFFERS:
⚠️ neuvelys — Research PENDING (no data collected yet)
READY TO PRODUCE:
✓ florayla — All gates passed. Run /produce-offer florayla
MODE B: Single Offer Detailed Report (with offer name)
When $ARGUMENTS contains an offer name, display detailed report and optionally generate production brief.
Step 1: Locate the Offer
find ~/copywriting-ecosystem -name "CONTEXT.md" -path "*$ARGUMENTS*" 2>/dev/null | head -3
Step 2: Read All State Files
Read and display from:
CONTEXT.md— product type, niche, avatar, mechanismhelix-state.yaml— all HELIX phase statusesmecanismo-unico.yaml— MUP, MUS, Gimmick Name, stateproject_state.yaml— current phase, next actionresearch/synthesis.md— confidence level (if exists)
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.
- 11d ago First seen · 166 lines · 14 tokens per session scan A d91769ef78c3
production-brief is a command published in the GitHub repository lckx777/copy-chief-black (5 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 1,491 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 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.