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/ingest)<a href="https://agentmods.dev/commands/lckx777/copy-chief-black/ingest"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/ingest/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/ingest"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/ingest.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.00016 | $0.00972 |
| Opus 5 | $0.00008 | $0.00486 |
| Sonnet 5 | $0.00003 | $0.00194 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade A, and why
ingest 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ingest — Content Ingestion Pipeline
Input: $ARGUMENTS
Processes any source through the 7-stage Content Ingestion Pipeline (S34).
What it Does
Routes the input through these 7 stages in sequence:
| Stage | Name | What Happens |
|---|---|---|
| 1 | Route | Detect source type (URL, PDF, folder, markdown) and select extractor |
| 2 | Chunk | Smart semantic chunking with 10% overlap to preserve boundaries |
| 3 | Canonicalize | Entity dedup via Jaccard similarity + fuzzy matching |
| 4 | Extract | Pull insights: frameworks, claims, VOC quotes, metrics |
| 5 | Synthesize | Append to dossier (append-only, never rewrites existing content) |
| 6 | Cross-Reference | Link against existing knowledge in ~/.claude/knowledge/ |
| 7 | Enrich | Suggest additions to expert profiles in ~/.claude/copy-squad/ |
Instructions
When this command is invoked with $ARGUMENTS:
Step 1: Parse Input
Extract the source path or URL from $ARGUMENTS.
If $ARGUMENTS is empty, respond:
Usage: /ingest <path-or-url>
Examples:
/ingest ~/Downloads/copywriting-book.pdf
/ingest ~/copywriting-ecosystem/swipes/vsl-competitor.md
/ingest https://example.com/article
Step 2: Validate Source
Check if the source exists:
- For file paths: verify the file exists with
ls <path> - For URLs: proceed (validation happens in the pipeline)
If the file does not exist, report the error and stop.
Step 3: Check for Duplicate Processing
bun run ~/copywriting-ecosystem/scripts/processing-registry.ts check "$ARGUMENTS" 2>/dev/null
If already processed, show when it was processed and ask:
This source was already ingested on [date].
Re-ingest? (Will append new insights only — no duplication via Jaccard dedup)
Step 4: Run the Ingestion Pipeline
bun run ~/copywriting-ecosystem/scripts/content-ingestion/pipeline.ts "$ARGUMENTS"
Display live progress for each stage as it completes.
Step 5: Report Output
After pipeline completes, report:
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 · 128 lines · 16 tokens per session scan A eb3dd134f1b2
ingest is a command published in the GitHub repository lckx777/copy-chief-black (5 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 972 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
brand-generate
Generate an on-brand document from a saved Brand Profile.
prose-review-docs
Reviews markdown documentation files or directories against the active prose style rules — the plugin's vendor-neutral baseline plus your organization's overlay when one is configured. Accepts a file path or directory (recursive). Runs prose-style-checker and optionally Vale. Supports --fix to auto-apply safe…
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
render-figures
Compile all .tex and .typ figure files in a directory.
harness-onboarding
Generate a human-readable onboarding document from HARNESS.md, AGENTS.md, and REFLECTIONLOG.md — a friendly guide for new team members.