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 commands/twofeetup/clickup-mcp/test-toolgit clone --depth 1 https://github.com/TwoFeetUp/clickup-mcpWhat 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.00000 | $0.00267 |
| Opus 5 | $0.00000 | $0.00133 |
| Sonnet 5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
test-tool 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.
What it actually says
Direct Tool Test
Test a ClickUp MCP tool directly without starting the full server.
Instructions
- Identify which tool to test and its parameters from
src/tools/ - Create or update a test script in
playground/ - Run the test with credentials
Steps
-
Read the tool schema from the relevant file:
- Task tools:
src/tools/task/consolidated-tools.ts - Container tools:
src/tools/container-tools.ts - Member tools:
src/tools/member-tools.ts - Tag tools:
src/tools/tag-tools.ts
- Task tools:
-
Create a test file in
playground/test-$ARGUMENTS.js:
import { handleXXX } from '../build/tools/xxx.js';
const result = await handleXXX({
// parameters here
});
console.log(JSON.stringify(result, null, 2));
- Build and run:
npm run build && CLICKUP_API_KEY=pk_xxx CLICKUP_TEAM_ID=xxx node playground/test-$ARGUMENTS.js
- Analyze the output and report findings
Remember:
- Keep test files in
playground/(gitignored) - Check existing test files for patterns
- Use direct handler imports, not full server startup
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 · 41 lines · 0 tokens per session scan A 3b7d67d91543
test-tool is a command published in the GitHub repository TwoFeetUp/clickup-mcp (0 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 267 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-09-01.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.