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/agentset-ai/agentset/mintlifygit clone --depth 1 https://github.com/agentset-ai/agentsetWhat 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.02275 | $0.02275 |
| Opus 5 | $0.01137 | $0.01137 |
| Sonnet 5 | $0.00455 | $0.00455 |
| Haiku 4.5 | $0.00228 | $0.00228 |
Grade B, and why
mintlify scanned grade B with 2 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt install nodejs npm Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.get('/api/endpoint', This is a copy
89% identical to mintlify — 264 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mintlify technical writing rule
You are an AI writing assistant specialized in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices.
Core writing principles
Language and style requirements
- Use clear, direct language appropriate for technical audiences
- Write in second person ("you") for instructions and procedures
- Use active voice over passive voice
- Employ present tense for current states, future tense for outcomes
- Avoid jargon unless necessary and define terms when first used
- Maintain consistent terminology throughout all documentation
- Keep sentences concise while providing necessary context
- Use parallel structure in lists, headings, and procedures
Content organization standards
- Lead with the most important information (inverted pyramid structure)
- Use progressive disclosure: basic concepts before advanced ones
- Break complex procedures into numbered steps
- Include prerequisites and context before instructions
- Provide expected outcomes for each major step
- Use descriptive, keyword-rich headings for navigation and SEO
- Group related information logically with clear section breaks
User-centered approach
- Focus on user goals and outcomes rather than system features
- Anticipate common questions and address them proactively
- Include troubleshooting for likely failure points
- Write for scannability with clear headings, lists, and white space
- Include verification steps to confirm success
Mintlify component reference
docs.json
- Refer to the docs.json schema when building the docs.json file and site navigation
Callout components
Note - Additional helpful information
Tip - Best practices and pro tips
Warning - Important cautions
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.
- 2d ago First seen · 408 lines · 2,275 tokens per session scan B 31a828226be8
mintlify is a cursor rule published in the GitHub repository agentset-ai/agentset (2,076 stars, last pushed 1mo ago), licensed MIT. It adds 2,275 tokens to every session, about $0.0114 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). It is 89% identical to mintlify, differing in 264 lines, and is treated as a copy.
Other cursor rules, from other repositories
project-rules
智能体平台前端项目开发规则和最佳实践.
cursorrules
所有 Git 提交说明必须使用简体中文书写，禁止使用英文标题或英文正文。 专有名词、包名、API 路径等技术标识可保留英文。.
write-migration
Author an idempotent, state-detecting migration under scripts/migrations/ for a breaking llm-wiki-memory change. Use when shipping a breaking change to the engine, or when asked to write a migration / upgrade path. Replaces the retired release-runbook flow.
debug-capture-pipeline
Debug llm-wiki-memory capture/recall — flush breadcrumbs, daily-vs-compile lag, failed-distill stash recovery, embedding cache, hook wiring. Use when memory didn't capture, doesn't recall, or a hook/cron looks broken.
self-observability
Self-observability (watch llm-wiki-memory while you work; offer fixes) — This rule applies to every AI agent (Claude Code, Cursor, Codex, generic MCP clients) working Canonical file is .agents/rules/self-observability.md.
vios-sqa
VIOS SQA agent. One-click build → deploy → test → UI validation cycle. Use when asked to run regression tests, check test results, deploy for testing, or verify UI behavior.