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/clickup-setup)<a href="https://agentmods.dev/commands/lckx777/copy-chief-black/clickup-setup"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/clickup-setup/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/clickup-setup"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/clickup-setup.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.00000 | $0.00757 |
| Opus 5 | $0.00000 | $0.00378 |
| Sonnet 5 | $0.00000 | $0.00151 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
clickup-setup 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 9d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/clickup-setup — ClickUp Integration Setup
Set up ClickUp integration for an offer in the copywriting ecosystem.
Usage
/clickup-setup [offer-path]
Examples
/clickup-setup concursos/decifra-lei-seca
/clickup-setup saude/neuvelys
/clickup-setup relacionamento/quimica-amarracao
Instructions
When this command is invoked:
-
Validate offer exists:
ls ~/copywriting-ecosystem/{offer-path}/helix-state.yamlIf not found, show error and list available offers.
-
Check if already configured:
- Look for
{offer}/clickup-sync.yaml - If exists, show current config and ask to reconfigure
- Look for
-
Get ClickUp hierarchy: Use ClickUp MCP tools:
clickup_get_workspace_hierarchy → Find or create niche folder -
Create ClickUp structure: Run the sync engine to generate setup instructions:
bun run ~/.claude/scripts/clickup-sync-engine.ts setup {offer-path} -
Execute each MCP tool call: For each instruction from the sync engine:
- Create folder (if niche folder doesn't exist)
- Create list for the offer
- Create parent task
- Create 10 HELIX phase subtasks
- Create 3 gate tasks (Research, Briefing, Production)
- Create 4 deliverable tasks (VSL, LP, Creatives, Emails)
- Create 5 research tasks (VOC, Competitors, Mechanism, Avatar, Synthesis)
-
Save mapping file: Create
{offer}/clickup-sync.yamlwith all task IDs:workspace_id: "90133067831" space_id: "901313380205" folder_id: "{created-folder-id}" list_id: "{created-list-id}" parent_task_id: "{created-parent-task-id}" phase_tasks: fase_01: "{task-id}" # ... fase_02 through fase_10 gate_tasks: research: "{task-id}" briefing: "{task-id}" production: "{task-id}" deliverable_tasks: vsl: "{task-id}" landing_page: "{task-id}" creatives: "{task-id}" emails: "{task-id}" research_tasks: voc: "{task-id}" competitors: "{task-id}" mechanism: "{task-id}" avatar: "{task-id}" synthesis: "{task-id}" last_synced: "{current-timestamp}"
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.
- 9d ago First seen · 108 lines · 0 tokens per session scan A 9c714cfe6abf
clickup-setup is a command published in the GitHub repository lckx777/copy-chief-black (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 757 tokens. 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
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.