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-readmegit 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.00235 |
| Opus 5 | $0.00000 | $0.00118 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
documentation-readme 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
README Maintenance
Keep README.md as the authoritative project overview. Update it when:
- Dependencies or system requirements change (Ruby, Node, PostgreSQL, Redis versions)
- Setup steps change (new env vars, new services, Docker changes)
- Major architectural decisions are made (new service integrations, auth changes)
Required Sections
- Project overview — what Links does
- Requirements — Ruby, Node, PostgreSQL, Redis versions
- Setup — clone, env config, Docker Compose, database setup
- Running locally —
docker compose -f docker-compose.dev.yml up, accessing the app - Testing —
docker compose -f docker-compose.test.yml run --rm test - Linting —
docker compose -f docker-compose.lint.yml run --rm rubocop - Deployment — GitHub Actions CI/CD, Docker image releases
- Architecture — key directories, service objects, background jobs
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 · 25 lines · 0 tokens per session scan A ae95822c6072
documentation-readme 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 235 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.