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 instructions/nicholasbester/clickup-cli/claude-mdgit clone --depth 1 https://github.com/nicholasbester/clickup-cliWhat 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.03710 | $0.03710 |
| Opus 5 | $0.01855 | $0.01855 |
| Sonnet 5 | $0.00742 | $0.00742 |
| Haiku 4.5 | $0.00371 | $0.00371 |
Grade A, and why
clickup-cli CLAUDE.md 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 2d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
clickup-cli
Rust CLI for the ClickUp API, optimized for AI agent consumption. Covers all ~130 endpoints across 28 resource groups and 4 utility commands.
Build & Test
cargo build # Build
cargo test # Run all tests
cargo test --test test_cli # CLI smoke tests only
cargo test --test test_output # Output formatting tests only
cargo run -- --help # Show help
Architecture
- Ships two binaries:
clickup-cli(canonical) andclkup(short alias, identical behaviour) - Entry:
src/main.rs→src/lib.rs - Commands:
src/commands/{resource}.rs— one file per API resource group - Models:
src/models/{resource}.rs— serde structs for API responses - Core:
src/client.rs(HTTP + retry),src/config.rs(TOML),src/output.rs(formatting),src/error.rs(errors)
CLI Pattern
clickup-cli <resource> <action> [ID] [flags]
Command Groups
Core (v0.1)
setup— configure API token and default workspaceauth— whoami, checkworkspace— list, seats, planspace— list, get, create, update, deletefolder— list, get, create, update, deletelist— list, get, create, update, delete, add-task, remove-tasktask— list, search, get, create, update, delete, time-in-status, add-tag, remove-tag, add-dep, remove-dep, link, unlink, move, set-estimate, replace-estimates
Collaboration (v0.2)
checklist— create, update, delete, add-item, update-item, delete-itemcomment— list, create, update, delete, replies, replytag— list, create, update, deletefield— list, set, unsettask-type— listattachment— list, upload
Tracking (v0.3)
time— list, get, current, create, update, delete, start, stop, tags, add-tags, remove-tags, rename-tag, historygoal— list, get, create, update, delete, add-kr, update-kr, delete-krview— list, get, create, update, delete, tasksmember— listuser— invite, get, update, remove
Communication (v0.4)
chat— channel-list, channel-create, channel-get, channel-update, channel-delete, channel-followers, channel-members, dm, message-list, message-send, message-update, message-delete, reaction-list, reaction-add, reaction-remove, reply-list, reply-send, tagged-usersdoc— list, create, get, pages, add-page, page, edit-page, embed-imagewebhook— list, create, update, deletetemplate— list, apply-task, apply-list, apply-folder
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.
- 2d ago First seen · 147 lines · 3,710 tokens per session scan A 380603459987
clickup-cli CLAUDE.md is an instructions file published in the GitHub repository nicholasbester/clickup-cli (45 stars, last pushed 4d ago), licensed Apache-2.0. It adds 3,710 tokens to every session, about $0.0186 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.