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/romkey/i2c-directory/documentation-user-guidegit clone --depth 1 https://github.com/romkey/I2C-DirectoryWhat 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.00246 |
| Opus 5 | $0.00000 | $0.00123 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
documentation-user-guide 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 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.
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
User Guide Maintenance
Update docs/USER_GUIDE.md whenever user-facing functionality is added or changed.
Structure
The guide has two types of sections:
Major Feature Sections
Dedicated sections for large functional areas. Each should cover:
- What the feature does
- How to access it
- Key concepts and terminology
- Step-by-step workflows with screenshots or descriptions
How-To Section
A collection of focused, task-oriented entries for small things users need to do. Each entry should:
- Have a clear action-oriented title (e.g., "How to link a Ko-fi payment to a member")
- Be self-contained — a user can follow it without reading other sections
- Be concise — numbered steps, no unnecessary background
When to Update
- New feature: Add a major section or how-to entry depending on scope
- Changed feature: Update the existing section to reflect the new behavior
- Removed feature: Remove or mark as deprecated
- New integration: Add a section explaining setup and usage from the user's perspective
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 · 36 lines · 0 tokens per session scan A bdd24d0c14b1
documentation-user-guide is a cursor rule published in the GitHub repository romkey/I2C-Directory (11 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 246 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-08-30.
Other cursor rules, from other repositories
cursorrules
🚨 ABSOLUTELY FORBIDDEN: Direct python/python3 execution.
cursorrules
This is an embedded systems project for the ESP32-S3-Touch-LCD-1.85C device. All development must strictly follow the project constitution located at .cursor/rules.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.