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/tam159/next-role/context7git clone --depth 1 https://github.com/tam159/next-roleWhat 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.00251 | $0.00251 |
| Opus 5 | $0.00125 | $0.00125 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
context7 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 yesterday.
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
Context7 Documentation Rule
Use Context7 MCP to fetch current documentation whenever the user asks about a library, framework, SDK, API, CLI tool, or cloud service. This includes API syntax, configuration, version migrations, library-specific debugging, setup instructions, and CLI usage.
Use Context7 even for familiar tools such as React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Prefer it over web search for library docs.
Do not use Context7 for refactoring, writing scripts from scratch, debugging business logic, code review, or general programming concepts.
Workflow:
- Start with
resolve-library-idusing the library name and the user's question, unless the user provides an exact library ID in/org/projectformat. - Pick the best match by exact name, relevance, snippet count, source reputation, and benchmark score.
- Query docs with the selected library ID and the user's full question.
- If the answer is not good enough, query again with research mode when available.
- Answer using the fetched docs.
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.
- yesterday First seen · 28 lines · 251 tokens per session scan A 802e59baee78
context7 is a cursor rule published in the GitHub repository tam159/next-role (48 stars, last pushed 2d ago), licensed MIT. It adds 251 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
settings-page
Settings page layout, tabs, Preferences section, AI Setup section, auto-save pattern, custom UI components.
rolemule-core
Core RoleMule conventions — app name, error system, JSON serialization, background tasks.
analytics-consent-onboarding
PostHog analytics, GDPR cookie consent, and onboarding tour usage.
verify-ai-readiness
Holistic assessment of the AI knowledge layer on a 5-level maturity scale; flags agent-blocking gaps.
03-skill-testcases
SKILL: Generate Test Scenarios Matrix from API spec (use for /api-isolated-tests).
01-qa-agent
QA AGENT PERSONA: Principles, Anti-patterns, workflows.