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/extract-dna)<a href="https://agentmods.dev/commands/lckx777/copy-chief-black/extract-dna"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/extract-dna/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/extract-dna"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/extract-dna.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.00018 | $0.01678 |
| Opus 5 | $0.00009 | $0.00839 |
| Sonnet 5 | $0.00004 | $0.00336 |
| Haiku 4.5 | $0.00002 | $0.00168 |
Grade A, and why
extract-dna 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 10d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/extract-dna — Extract DNA from Content
Input: $ARGUMENTS
Runs the 5-layer DNA extraction from the System Cloning pipeline (S37) on any content file. Produces structured knowledge: frameworks, principles, methodologies, heuristics, and dilemmas.
What It Extracts
| Layer | What it Captures | Examples |
|---|---|---|
| Philosophy | Core principles and beliefs | "Copy confortavel = copy que falhou" |
| Frameworks | Named structural models | RMBC, HELIX, 5 Lentes de Validacao |
| Heuristics | Decision shortcuts and rules of thumb | "If DRE < level 3, escalate to level 4" |
| Methodologies | Step-by-step processes and workflows | Constraint Progressivo 4 iterations |
| Dilemmas | Trade-offs, edge cases, tensions | "Specificity vs broad appeal for cold traffic" |
Instructions
When this command is invoked with $ARGUMENTS:
Step 1: Validate Input
If $ARGUMENTS is empty:
Usage: /extract-dna <path-to-content>
Examples:
/extract-dna ~/Downloads/scientific-advertising.pdf
/extract-dna ~/copywriting-ecosystem/swipes/competitor-vsl.md
/extract-dna ~/copywriting-ecosystem/saude/florayla/research/synthesis.md
For expert web-based cloning, use /clone-expert instead.
Verify the file exists:
ls "$ARGUMENTS" 2>/dev/null
If not found, report error and stop.
Step 2: Check Quality Threshold
Before running full extraction, estimate content size:
bun run ~/copywriting-ecosystem/scripts/system-cloning/quality-threshold.ts status 2>/dev/null
Also estimate reading time from file size (rough: 1KB ≈ 1 min reading at 200wpm):
wc -w "$ARGUMENTS" 2>/dev/null
Display the quality assessment:
QUALITY GATE CHECK
File: [filename]
Size: [X] words / ~[Y] min reading time
Cumulative ingested: [Z] hours total
Status: [SUFFICIENT_DATA ≥ 100h | INSUFFICIENT_DATA < 100h]
If INSUFFICIENT_DATA, warn:
⚠️ WARNING: Total ingested content < 100h reading time.
DNA extraction will be marked as SPECULATIVE.
Results are useful but may be incomplete or biased by limited training data.
Continue anyway? (y/n)
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.
- 10d ago First seen · 194 lines · 18 tokens per session scan A 59e313b32c3a
extract-dna is a command published in the GitHub repository lckx777/copy-chief-black (5 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 1,678 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.