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/sync-project)<a href="https://agentmods.dev/commands/lckx777/copy-chief-black/sync-project"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/sync-project/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/sync-project"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/sync-project.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.00007 | $0.00449 |
| Opus 5 | $0.00003 | $0.00225 |
| Sonnet 5 | $0.00001 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
sync-project 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 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.
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.
What it actually says
Sync to Claude.ai Project
Sync offer $ARGUMENTS to Claude.ai
Files to Sync
From local to Claude.ai Knowledge Base:
research/$ARGUMENTS/synthesis.md→ Project KBbriefings/$ARGUMENTS/helix-complete.md→ Project KBproduction/$ARGUMENTS/reviews/final-review.md→ Project KB
Sync Checklist
- Export synthesis.md
- Export helix-complete.md
- Export final deliverables
- Update Project Instructions with current phase
Sync Process
Step 1: Prepare Files
# Create export directory
mkdir -p ~/copywriting-ecosystem/export/$ARGUMENTS
# Copy key files
cp research/$ARGUMENTS/synthesis.md ~/copywriting-ecosystem/export/$ARGUMENTS/
cp briefings/$ARGUMENTS/helix-complete.md ~/copywriting-ecosystem/export/$ARGUMENTS/
cp production/$ARGUMENTS/reviews/final-review.md ~/copywriting-ecosystem/export/$ARGUMENTS/ 2>/dev/null || true
Step 2: Open Claude.ai
- Navigate to claude.ai
- Open or create Project for this offer
- Upload files from export directory to Knowledge Base
Step 3: Update Project Instructions
Add to Project Custom Instructions:
## Estado Atual
- Fase: [current phase]
- Última sync: [date]
- Key decisions synced: [list]
## Arquivos Disponíveis
- synthesis.md: Pesquisa consolidada
- helix-complete.md: Briefing estratégico
- final-review.md: Validações (se existir)
Alternative: /teleport
For interactive refinement with full context:
/teleport
Transfers conversation context to Claude.ai web interface.
Post-Sync
- ✅ Confirm files uploaded to Project KB
- ✅ Update Project Instructions
- ✅ Start polish session in Claude.ai
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 · 70 lines · 7 tokens per session scan A 26432cc1aa80
sync-project is a command published in the GitHub repository lckx777/copy-chief-black (5 stars, last pushed 6mo ago), licensed MIT. It adds 7 tokens to every session and 449 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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.