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/status)<a href="https://agentmods.dev/commands/lckx777/copy-chief-black/status"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/status/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/status"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/status.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.00000 | $0.00573 |
| Opus 5 | $0.00000 | $0.00287 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
status 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 7d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/status — System-Wide Status Dashboard
Show the complete Copy Chief BLACK system status.
Instructions
When this command is invoked, execute these steps IN ORDER:
1. System Info
Read ~/.claude/manifest.yaml and display:
- System name and version
- Current level (1-4)
- Date of last manifest update
2. Decision Engine (if available)
Check if ~/.claude/scripts/decision-engine.ts exists. If so, run:
bun run ~/.claude/scripts/decision-engine.ts 2>/dev/null
Display the prioritized offer recommendations.
3. Self-Healing Queue (if available)
Check if ~/.claude/scripts/retry-processor.ts exists. If so, run:
bun run ~/.claude/scripts/retry-processor.ts --status 2>/dev/null
Display any queued retries. If the script does not exist, check if ~/.claude/knowledge/retry-queue.yaml exists and display its contents.
4. All Offers Status
Find all helix-state.yaml files in ~/copywriting-ecosystem and for EACH offer display:
- Offer name and niche
- Current phase (IDLE / RESEARCH / BRIEFING / PRODUCTION / DELIVERED)
- Gates passed (research, briefing, production)
- Mecanismo state (UNDEFINED / DRAFT / VALIDATED / APPROVED)
- Last activity date
Use this command to discover offers:
find ~/copywriting-ecosystem -name "helix-state.yaml" -type f 2>/dev/null
5. Pipeline Status
Check for any active pipeline states:
find ~/copywriting-ecosystem -name "pipeline-state.json" -type f 2>/dev/null
If found, display current step, last checkpoint, and any blocked human gates.
6. Summary Table
Present a consolidated summary:
| Metric | Value |
|---------------------|-------|
| Total Offers | X |
| IDLE | X |
| RESEARCH | X |
| BRIEFING | X |
| PRODUCTION | X |
| DELIVERED | X |
| Avg Quality Score | X.X |
| Retry Queue | X |
| System Level | 4 |
7. Recommended Next Action
Based on the analysis above, recommend the single highest-priority next action the user should take. Consider:
- Offers closest to delivery (high ROI to finish)
- Blocked human gates that need approval
- Failed validations that need attention
- New offers that should start research
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.
- 7d ago First seen · 72 lines · 0 tokens per session scan A 29d9a8c20cff
status is a command published in the GitHub repository lckx777/copy-chief-black (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 573 tokens. 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.