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/create-offer)<a href="https://agentmods.dev/commands/lckx777/copy-chief-black/create-offer"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/create-offer/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/create-offer"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/create-offer.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.00008 | $0.02362 |
| Opus 5 | $0.00004 | $0.01181 |
| Sonnet 5 | $0.00002 | $0.00472 |
| Haiku 4.5 | $0.00001 | $0.00236 |
Grade A, and why
create-offer 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 8d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Offer Pipeline
Creates a complete offer structure for: $ARGUMENTS
This command runs a 3-step pipeline:
- create-niche-pack.ts — Generates niche library and templates (if niche is new)
- offer-elicitation.ts — Generates YAML setup template, human fills it, then scaffolds offer
- workflow-generator.ts — Generates
workflow.yamlfor bob-orchestrator to consume
Step 0: Parse Arguments
NICHO=$(echo "$ARGUMENTS" | cut -d' ' -f1)
OFERTA=$(echo "$ARGUMENTS" | cut -d' ' -f2)
BASE=~/copywriting-ecosystem/$NICHO/$OFERTA
NICHE_LIBRARY=~/copywriting-ecosystem/$NICHO/biblioteca_nicho_${NICHO}_CONSOLIDADA.md
Step 1: Create Niche Pack (if niche is new)
Check whether the niche library already exists:
if [ ! -f "$NICHE_LIBRARY" ]; then
echo "Niche '$NICHO' is new — generating niche expansion pack..."
bun run ~/.claude/scripts/create-niche-pack.ts --niche "$NICHO" --offer "$OFERTA"
else
echo "Niche '$NICHO' already exists — skipping niche pack creation."
echo "Library: $NICHE_LIBRARY"
fi
create-niche-pack.ts generates:
$NICHO/biblioteca_nicho_${NICHO}_CONSOLIDADA.md— Niche library skeleton$NICHO/_templates/— Niche-adapted templates (voc extraction, ads spy, etc.)- If
--offeris also passed: full offer scaffolding (CONTEXT.md, helix-state.yaml, mecanismo-unico.yaml, task_plan.md, full directory tree)
When niche already exists, skip this step entirely to avoid overwriting an existing library.
Step 1.5: 3-Pass Exploration (AIOS Pattern)
Before scaffolding the offer, run a structured 3-pass exploration to map the territory. This prevents creating in a vacuum.
Pass 1: Topologia do Nicho
Read the niche library (biblioteca_nicho_${NICHO}_CONSOLIDADA.md) and map:
- How many offers already exist in this niche?
- What VOC data is already collected cross-offer?
- What clichés are documented (to avoid from day 1)?
- What experts have relevant coverage?
Pass 2: Contratos e Concorrentes
Check the competitive landscape:
- Read any existing
research/competitors/summary.mdfrom sibling offers in the same niche - Check if
ads-library-spy.mdexists for similar offers - Identify what angles are already being used (to differentiate)
- List any cross-offer dependencies (e.g., front-end → SaaS upsell)
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.
- 8d ago First seen · 246 lines · 8 tokens per session scan A c5b3fa3c360f
create-offer is a command published in the GitHub repository lckx777/copy-chief-black (5 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 2,362 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.