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/build-verifygit 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/build-verify)<a href="https://agentmods.dev/commands/twofeetup/clickup-mcp/build-verify"><img src="https://agentmods.dev/badge/commands/twofeetup/clickup-mcp/build-verify.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.00212 |
| Opus 5 | $0.00000 | $0.00106 |
| Sonnet 5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
build-verify 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.
What it actually says
Build and Verify
Run TypeScript compilation and verify the build succeeds.
Steps
- Run the TypeScript compiler:
npm run build
- If build succeeds, verify the output:
ls -la build/
-
If build fails, analyze the error:
- Read the error messages carefully
- Identify the failing file and line
- Fix the TypeScript errors
- Re-run build
-
Report the build status to user
Common Build Issues
- Missing imports: Check
src/tools/index.tsandsrc/services/clickup/index.tsfor exports - Type errors: Check
src/services/clickup/types.tsfor type definitions - Module resolution: Ensure
.jsextensions in import paths (NodeNext modules)
Success Criteria
Build is successful when:
- No compilation errors
build/directory contains compiled.jsfiles- Entry point
build/index.jsexists
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 · 37 lines · 0 tokens per session scan A c3107d5bb78c
build-verify 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 212 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
types
Debug and fix TypeScript type errors with systematic analysis and expert guidance.
setup-code-intelligence
Check code-intelligence prerequisites (ripgrep + a language server) and print install hints.
type-crusade
Unleash parallel TypeScript Purist agents to purge every any, as cast, and type sin across the codebase. No type sin survives.
vite-react-setup
Setup project React SPA mới với Vite + TypeScript + Tailwind CSS v3 + Vitest. Dùng khi bắt đầu dự án frontend mới, cần scaffold đầy đủ config, brand KZTEK colors, và test setup sẵn sàng.
typescript
Apply TypeScript best practices and coding standards.
scaffold-react
Quickly scaffold a new React + TypeScript project with Claude Code configuration.