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/overnight)<a href="https://agentmods.dev/commands/lckx777/copy-chief-black/overnight"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/overnight/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/overnight"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/overnight.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.00012 | $0.01399 |
| Opus 5 | $0.00006 | $0.00700 |
| Sonnet 5 | $0.00002 | $0.00280 |
| Haiku 4.5 | $0.00001 | $0.00140 |
Grade B, and why
overnight scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
from `~/.claude/config/overnight.yaml` and executes workflow loops for each How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/overnight — Overnight Production Loop
Triggers and manages the autonomous overnight production engine (S30). Runs all configured deliverables (VSL, LP, Creatives, Emails) sequentially with automatic halt criteria, state persistence, and morning report generation.
Subcommands
| Subcommand | Action |
|---|---|
/overnight start <offer> |
Start overnight loop for an offer |
/overnight status [offer] |
Check running or completed loop status |
/overnight stop <offer> |
Gracefully stop a running loop |
/overnight report <offer> |
Generate or view the morning report |
/overnight help |
Show this help |
Usage
/overnight start <offer>
Starts the overnight production loop for the specified offer. Reads configuration
from ~/.claude/config/overnight.yaml and executes workflow loops for each
configured deliverable in priority order.
What it does:
- Reads overnight config (deliverables, halt criteria, max wall time)
- Creates state file at
{offer}/production/overnight-state/overnight-state.yaml - Executes
workflow-loops/executor.tsfor each deliverable (in Claude context: dispatches to persona subagents) - Evaluates halt criteria after each iteration
- Generates morning report on completion
Halt criteria:
- Score drops 2+ iterations in a row → HALT that deliverable
- 3 consecutive failures below threshold → HALT + flag for Conclave
.overnight-stopsentinel file detected → graceful stop- Max wall time (default 4h) reached → stop all
- All deliverables passed → DONE
Examples:
bun run scripts/auto-production-loop.ts start --offer florayla
bun run scripts/auto-production-loop.ts start --offer neuvelys --config ~/my-overnight.yaml
/overnight status [offer]
Displays current state of the overnight loop for an offer.
Shows:
- Loop status (running / complete / halted / stopped)
- Per-deliverable status, final scores, iterations used, units passed
- Runtime so far vs maximum wall time
- Any halt reasons
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 · 178 lines · 12 tokens per session scan B 996dbb021bd8
overnight is a command published in the GitHub repository lckx777/copy-chief-black (5 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 1,399 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.