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/add-toolgit 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/add-tool)<a href="https://agentmods.dev/commands/twofeetup/clickup-mcp/add-tool"><img src="https://agentmods.dev/badge/commands/twofeetup/clickup-mcp/add-tool.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.00000 | $0.00604 |
| Opus 5 | $0.00000 | $0.00302 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
add-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 3d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add New Tool
Guide for adding a new MCP tool to the ClickUp server.
Before Starting
- Read
MCP_DESIGN_PRINCIPLES.mdfor AI-first design guidelines - Check if functionality can be added to an existing consolidated tool
- Consider: Does this tool follow user intent or API structure?
Steps
1. Design the Tool Schema
Create or update tool schema in src/tools/:
- Task-related:
src/tools/task/consolidated-tools.ts - Container-related:
src/tools/container-tools.ts - New category: Create
src/tools/$ARGUMENTS-tools.ts
export const myNewTool = {
name: "tool_name",
description: "AI-friendly description of what this tool does. Include when to use it.",
inputSchema: {
type: "object",
properties: {
action: {
type: "string",
enum: ["get", "create", "update", "delete"],
description: "REQUIRED: Operation to perform"
},
// ... other parameters
},
required: ["action"]
}
};
2. Implement the Handler
Create handler in corresponding file:
export async function handleMyNewTool(params: any) {
const { action, ...rest } = params;
// Validate required parameters
if (!action) {
return { isError: true, content: [{ type: "text", text: "Missing required parameter: action" }] };
}
// Route to appropriate action
switch (action) {
case "get": return handleGet(rest);
case "create": return handleCreate(rest);
default: return { isError: true, content: [{ type: "text", text: `Unknown action: ${action}` }] };
}
}
3. Register the Tool
In src/server.ts:
- Import the tool schema and handler
- Add tool to
ListToolsRequestSchemahandler - Add case to
CallToolRequestSchemaswitch statement
4. Test
npm run build
# Create test in playground/
CLICKUP_API_KEY=pk_xxx CLICKUP_TEAM_ID=xxx node playground/test-new-tool.js
5. Document
Update root CLAUDE.md with new tool in "Available MCP Tools" section.
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.
- 3d ago First seen · 90 lines · 0 tokens per session scan A 8cf34b170bba
add-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 604 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.