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/update-ecosystem)<a href="https://agentmods.dev/commands/lckx777/copy-chief-black/update-ecosystem"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/update-ecosystem/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/update-ecosystem"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/update-ecosystem.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.00013 | $0.02547 |
| Opus 5 | $0.00006 | $0.01273 |
| Sonnet 5 | $0.00003 | $0.00509 |
| Haiku 4.5 | $0.00001 | $0.00255 |
Grade D, and why
update-ecosystem scanned grade D with 2 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 7d 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.
VERSION=$(grep "^VERSION=" ~/.claude/.version | cut -d= -f2) Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$BUILD_DIR" How it starts
The opening of the file, as written. The whole thing — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/update-ecosystem - Backup Completo do Ecossistema
Gera um ZIP com TUDO do ecossistema Claude Code usando descoberta automática.
Filosofia: Incluir TUDO, excluir apenas auto-gerados.
FASE 0: IDENTIFICAR VERSÃO (Automático)
# Ler versão de ~/.claude/.version (Single Source of Truth)
VERSION=$(grep "^VERSION=" ~/.claude/.version | cut -d= -f2)
RELEASED=$(grep "^RELEASED=" ~/.claude/.version | cut -d= -f2)
TIMESTAMP=$(date +%Y%m%d-%H%M)
echo "Versão: v$VERSION"
echo "Released: $RELEASED"
echo "Timestamp: $TIMESTAMP"
Se .version não existe:
# Criar com versão atual
echo "VERSION=4.9.3" > ~/.claude/.version
echo "RELEASED=$(date +%Y-%m-%d)" >> ~/.claude/.version
FASE 1: SINCRONIZAR VERSÃO
# Propagar versão para todos os arquivos
~/.claude/scripts/sync-version.sh
# Verificar sincronização
~/.claude/scripts/sync-version.sh --check
❌ BLOQUEAR SE: Arquivos dessincronizados
FASE 2: PREPARAR DIRETÓRIO DE BUILD
BUILD_DIR="/tmp/eco-build-$TIMESTAMP"
PAYLOAD_DIR="$BUILD_DIR/ecossistema-v${VERSION}-installer/payload"
ZIP_NAME="ecossistema-v${VERSION}-installer.zip"
rm -rf "$BUILD_DIR"
mkdir -p "$PAYLOAD_DIR/.claude"
mkdir -p "$PAYLOAD_DIR/copywriting-ecosystem"
FASE 3: COPIAR ~/.claude/ (Descoberta Automática)
3.1 Definir Exclusões (Única Lista a Manter)
CLAUDE_EXCLUDES=(
"debug"
"cache"
"plans"
"session-env"
"shell-snapshots"
"file-history"
"projects"
"paste-cache"
"todos"
"tasks"
"telemetry"
"downloads"
"history.jsonl"
".DS_Store"
"statsig"
"memory.db"
"memory.db-wal"
"memory.db-shm"
"plugins/marketplaces"
"plugins/cache"
)
3.2 Copiar Tudo Exceto Exclusões
# Construir padrão de exclusão para rsync
EXCLUDE_PATTERN=""
for item in "${CLAUDE_EXCLUDES[@]}"; do
EXCLUDE_PATTERN="$EXCLUDE_PATTERN --exclude=$item"
done
# Copiar TUDO de ~/.claude/ exceto exclusões
rsync -av $EXCLUDE_PATTERN ~/.claude/ "$PAYLOAD_DIR/.claude/"
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.
- 7d ago First seen · 383 lines · 13 tokens per session scan D bd034306545a
update-ecosystem is a command published in the GitHub repository lckx777/copy-chief-black (5 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 2,547 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.