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/contributegit 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/contribute)<a href="https://agentmods.dev/rules/umijs/umi-mcp/contribute"><img src="https://agentmods.dev/badge/rules/umijs/umi-mcp/contribute.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.00179 | $0.00179 |
| Opus 5 | $0.00089 | $0.00089 |
| Sonnet 5 | $0.00036 | $0.00036 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
contribute 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
Contribution Guidelines
Getting Started
- Fork the repository
- Clone your fork
- Install dependencies with
pnpm install - Make your changes
- Run tests with
pnpm test - Submit a pull request
Pull Request Process
- Ensure your code follows the style guidelines
- Add tests for new features
- Update documentation if necessary
- Follow the commit message conventions
Development Workflow
- Use feature branches
- Keep pull requests focused on a single feature/fix
- Ensure all tests pass before submitting
- Follow the TypeScript coding standards
- Document any new MCP tools thoroughly
Release Process
- Releases are handled via
pnpm release - This creates a Git tag and GitHub release
- The release process also generates changelog entries
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 · 33 lines · 179 tokens per session scan A 34205bda98b3
contribute is a cursor rule published in the GitHub repository umijs/umi-mcp (21 stars, last pushed 1y ago), licensed MIT. It adds 179 tokens to every session, about $0.0009 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
release-checklist
What to update with each code change or version release.
release-policy
Release, versioning, and signing policy for setmac.
github-repo-triage
Triage and maintain GitHub repos — issues, PRs, cherry-picks, releases, publishing.
release
Automated release workflow — versioning, changelog generation, tagging.
npm-publish-agent
NPM Package Publishing Guidelines.
gitflow
Cursor rule "gitflow" from Wulnut/lark_agent, covering gitflow 工作流规则, 主分支, main（或master）, develop and 支持分支.