Borrowing it
Nothing to install: this file belongs to TwoFeetUp/clickup-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TwoFeetUp/clickup-mcp/main/.claude/commands/test-tool.mdgit clone --depth 1 https://github.com/TwoFeetUp/clickup-mcpWrote 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/twofeetup/clickup-mcp/test-tool)<a href="https://agentmods.dev/commands/twofeetup/clickup-mcp/test-tool"><img src="https://agentmods.dev/badge/commands/twofeetup/clickup-mcp/test-tool/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/twofeetup/clickup-mcp/test-tool"><img src="https://agentmods.dev/badge/commands/twofeetup/clickup-mcp/test-tool.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.00267 |
| Opus 5.5 | $0.00000 | $0.00107 |
| Sonnet 5.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 1mo 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.
- 1mo 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 6mo 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
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
check-dev
Type-check a Z specification with fuzz.