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.
npx agentmods add skills/ulises-jeremias/agent-toolkit/clickup-clinpx skills add ulises-jeremias/agent-toolkit --skill clickup-cligit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/skills/ulises-jeremias/agent-toolkit/clickup-cli)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/clickup-cli"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/clickup-cli.svg" alt="Measured on agentmods" 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 | $0.00065 | $0.00653 |
| Opus 5 | $0.00032 | $0.00327 |
| Sonnet 5 | $0.00013 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
clickup-cli 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 4d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClickUp CLI (clickup)
Use the clickup CLI instead of raw ClickUp API calls. Handles authentication, git integration,
fuzzy status matching, and custom fields automatically.
When to use
- Create, edit, view, or search ClickUp tasks
- Check sprint status or recent tasks
- Add comments, link PRs/branches, or manage statuses
- Task IDs:
CU-abc123or86abc123
Out of scope
- Does NOT replace project management decisions — confirm scope with user first
- Does NOT push code or create PRs — delegate to
github-cli-workflow
Authentication
clickup auth login # store API token
clickup auth status # verify
Config: ~/.config/clickup/config.yml. Supports per-directory defaults.
Key rules
- Always
--currentfor sprint lists — IDs change every sprint, never hardcode them - Fill ALL fields when creating tasks (name, description, status, priority, assignee, tags, due-date)
- Check
clickup tag listbefore using tags — reuse existing ones - Naming:
[Work Type] Context — Action (Platform/Scope)— seereferences/task-management.md - Bulk ops: pass multiple IDs as positional args; for subtasks view parent with
--jsonfirst
Quick commands
clickup task view # auto-detects from git branch
clickup task search "query"
clickup task recent --sprint
clickup task create --current --name "[Bug] Auth — Fix X (API)" --priority 2
clickup task edit CU-abc123 --status "in progress"
clickup status list # check valid statuses before setting
clickup sprint current
clickup inbox
Common flags
| Flag | Description |
|---|---|
--json |
JSON output |
--jq <expr> |
Filter with jq |
--raw, -r |
Raw strings with --jq |
References
references/task-management.md— full task view/search/create/edit, naming conventions, multi-list, checklists, git integrationreferences/time-tracking.md— log, list, timesheet commandsreferences/docs-management.md— Docs and Pages management
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 79 lines · 65 tokens per session scan A 70b8cd4895f4
clickup-cli is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 653 once invoked, about $0.0003 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-30.
Other skills, from other repositories
iblai-api-agent-support
Manage an ibl.ai agent's human-support tickets via the platform API — list and filter the tickets users raised with an agent (by agent, requester, status, session), read a ticket's conversation thread, reply as the support team, change ticket status, and close or delete tickets. Use when triaging or responding to…
github-navigator
GitHub operations via gh CLI. CRITICAL: Use instead of WebFetch for any github.com URL or GitHub repo path like owner/repo. Use when the user asks to inspect repositories, files, issues, pull requests, releases, Actions runs, or repository structure. Use when the user says 'show README', 'list issues', 'check PR'…
fusebase-dashboards
How to use MCP for working with FuseBase Project Dashboards during LLM development. Use when: 1. Discovering dashboards, views, and schema via MCP; 2. Reading or updating dashboard data; 3. Working with relations, filters, templates, and child tables; 4. Understanding dashboard/view structure before SDK runtime code…
breaking-down-work
Decomposes a goal, feature, epic, or deliverable into a structured task tree (tasks, subtasks, checklists) with dependencies in Astravue. Use when the user wants to break down, decompose, or plan out work, turn an epic or feature into tasks, "split this into tasks", scope a deliverable, or build a work breakdown…
capturing-meeting-actions
Extracts action items from meeting notes, transcripts, or a brain dump and creates them as owned, dated tasks in Astravue. Use when the user pastes meeting notes or a transcript, asks to turn notes or standup discussion into tasks, capture action items, or "make tasks out of this".
find-wasted-effort
Use when the operator runs "/find-wasted-effort" or asks about "wasted effort", "ceremony overhead", "process overhead", "outcome-neutral steps", "are our gate stops worth it", "is the Full lane overkill here", or wants the process-per-outcome sibling of /token-waste-audit. Audits Flow ARTIFACTS ON DISK (gate reports…