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.
npx agentmods add commands/lckx777/copy-chief-black/plan-executiongit 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/plan-execution)<a href="https://agentmods.dev/commands/lckx777/copy-chief-black/plan-execution"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/plan-execution.svg" alt="Measured on agentmods" 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.00006 | $0.00667 |
| Opus 5 | $0.00003 | $0.00333 |
| Sonnet 5 | $0.00001 | $0.00133 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
plan-execution 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 6d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Setup
Initialize planning structure for: $ARGUMENTS
Pre-Flight
- Verify working directory is a project folder
- Check if planning files already exist
Create Files
task_plan.md
Primary planning document with phases, gates, and status.
findings.md
Consolidated discoveries, VOC, and strategic decisions.
progress.md
Session log with actions, decisions, and next steps.
Workflow
Step 1: Check Existing
if [ -f task_plan.md ]; then
echo "⚠️ Planning files exist. Use /plan-reset to recreate."
exit 0
fi
Step 2: Create task_plan.md
# Task Plan: $ARGUMENTS
## Objetivo
[Descrição da oferta]
## Fases (HELIX System + Parallel Execution)
### PHASE 1: Parallel Research
**Command:** `/helix-parallel [offer]`
- [ ] VOC Research
- [ ] Competitor Analysis
- [ ] Mechanism Research
- [ ] Avatar Profiling
- [ ] Synthesis
**Gate:** synthesis.md exists
### PHASE 2: Strategic Briefing
**Tool:** helix-system-agent
- [ ] 10 HELIX phases
- [ ] copy-critic STAND on MUP/MUS
**Gate:** helix-complete.md exists
### PHASE 3: Parallel Production
**Command:** `/produce-offer [offer]`
- [ ] VSL Script
- [ ] Landing Page
- [ ] Ad Creatives
- [ ] Email Sequence
**Gate:** All deliverables complete
### PHASE 4: Review
**Command:** `/review-all [offer]`
- [ ] Internal review
- [ ] copy-critic validation
**Gate:** APPROVED verdict
### PHASE 5: Polish & Delivery
**Tool:** Claude.ai Project
- [ ] Sync
- [ ] Polish
- [ ] Deliver
Step 3: Create findings.md
# Findings: $ARGUMENTS
## VOC Research
[Populated by research phase]
## Strategic Decisions
### MUP
- Definition: [pending]
- Verdict: [pending]
### MUS
- Definition: [pending]
- Verdict: [pending]
Step 4: Create progress.md
# Progress: $ARGUMENTS
## Session 1: [DATE]
**Phase:** Setup
**Actions:**
- Created planning structure
**Next:**
- Run /helix-parallel
Output
After creation:
✅ Planning files created:
- task_plan.md (phases and gates)
- findings.md (discoveries)
- progress.md (session log)
Next: Edit task_plan.md with offer details, then /helix-parallel [offer]
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.
- 6d ago First seen · 128 lines · 6 tokens per session scan A ab5dcbd277d5
plan-execution is a command published in the GitHub repository lckx777/copy-chief-black (5 stars, last pushed 6mo ago), licensed MIT. It adds 6 tokens to every session and 667 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.