clickup-setup

clickup-setup is a command for Claude Code from lckx777/copy-chief-black. It costs 0 tokens per session (757 once invoked), scanned A, original, MIT.

A setup command that connects a copywriting offer project to ClickUp, a task and project management service.

In plain words
What is it for?
Use it to create or reconfigure an offer’s ClickUp structure, including phase, review-gate, and deliverable tasks.
Why use it?
It removes the manual work of building matching folders, lists, tasks, and workflow phases in ClickUp.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: reads .claude/ paths; mentions Claude Code.

Good fit Use it to create or reconfigure an offer’s ClickUp structure, including phase, review-gate, and deliverable tasks.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/lckx777/copy-chief-black/clickup-setup
Install

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.

Clone the repo
git clone --depth 1 https://github.com/lckx777/copy-chief-black

Made for: Claude Code.

Wrote 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.

agentmods badge for clickup-setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/lckx777/copy-chief-black/clickup-setup/github.svg)](https://agentmods.dev/commands/lckx777/copy-chief-black/clickup-setup)
Your own site
<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.

agentmods 80×15 button for clickup-setup

Your own site · 80×15
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 757 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash 9c714cfe6abf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

framework/commands/clickup-setup.md · 108 lines

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:

  1. Validate offer exists:

    ls ~/copywriting-ecosystem/{offer-path}/helix-state.yaml
    

    If not found, show error and list available offers.

  2. Check if already configured:

    • Look for {offer}/clickup-sync.yaml
    • If exists, show current config and ask to reconfigure
  3. Get ClickUp hierarchy: Use ClickUp MCP tools:

    clickup_get_workspace_hierarchy → Find or create niche folder
    
  4. Create ClickUp structure: Run the sync engine to generate setup instructions:

    bun run ~/.claude/scripts/clickup-sync-engine.ts setup {offer-path}
    
  5. 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)
  6. Save mapping file: Create {offer}/clickup-sync.yaml with 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}"
    

Read the full file on GitHub · 108 lines

Changes

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.

  1. 9d ago First seen · 108 lines · 0 tokens per session scan A 9c714cfe6abf

Subscribe to this mod's changes

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.