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 rules/umijs/umi-mcp/mcpgit clone --depth 1 https://github.com/umijs/umi-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/rules/umijs/umi-mcp/mcp)<a href="https://agentmods.dev/rules/umijs/umi-mcp/mcp"><img src="https://agentmods.dev/badge/rules/umijs/umi-mcp/mcp.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.00269 | $0.00269 |
| Opus 5 | $0.00134 | $0.00134 |
| Sonnet 5 | $0.00054 | $0.00054 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
mcp 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
MCP Tools Implementation
Tool Structure
- All MCP tools should follow a consistent structure
- Each tool is defined in
src/tools/with a prefix ofumi- - Tools should export a function that returns a
Toolobject - Tools should define input and output schemas
Input/Output Schemas
- Define input schemas using zod
- Define output schemas to match expected return values
- Follow MCP spec for schema definitions
- Use descriptive names for schema properties
Error Handling
- Use proper error handling with descriptive messages
- Return structured error responses when appropriate
- Validate inputs before processing
Tool Implementation
- Keep tool implementations focused on a single responsibility
- Reuse common code for similar tools (like config management)
- Document tools with clear descriptions
- Export tools in the
src/index.tsfile for consumption
Examples
- Config tools: umi-config.ts
- Generator tools: umi-generate.ts
- Data retrieval tools: umi-route-list.ts
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 · 35 lines · 269 tokens per session scan A 8060c1ea0e25
mcp is a cursor rule published in the GitHub repository umijs/umi-mcp (21 stars, last pushed 1y ago), licensed MIT. It adds 269 tokens to every session, about $0.0013 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.