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/testinggit 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.00280 |
| Opus 5 | $0.00000 | $0.00140 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
testing 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
Testing
- Framework: Minitest 5 with Rails test helpers
- Fixtures: YAML fixtures in
test/fixtures/;fixtures :allis set intest_helper.rb - Parallelization: Tests run in parallel by processor count
- Run tests:
docker compose -f docker-compose.test.yml run --rm test
Conventions
- Write tests for every change; write regression tests for every bug fix
- Place model tests in
test/models/, controller tests intest/controllers/, service tests intest/services/ - Use
assert_*methods, not RSpec-styleexpect - Use
setupandteardownmethods for test lifecycle, notbefore/after - System tests use Capybara with Selenium Chrome — place in
test/system/ - Stub external API calls (OIDC provider, etc.) in tests — never hit real APIs
# ✅ Standard test structure
class MemberTest < ActiveSupport::TestCase
setup do
@member = members(:active_member)
end
test 'should be valid with required attributes' do
assert @member.valid?
end
end
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 · 35 lines · 0 tokens per session scan A d5deb44f0750
testing 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 280 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.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rules for Cypress development with E2E testing.
dev-browser
Fallback browser automation with persistent Chrome state. Use only when Browser Use is unavailable or blocked.
security-standards
Cursor rule "security-standards" from wjgogogo/cursor-rules, covering 安全规范, 核心原则 [p0], 输入验证, xss 防护 and csrf 防护.
scrapy
Cursor rule "scrapy" from Solihatun1/AI-Cursor-Scraping-Assistant, covering scrapy best practices, 1. code organization and structure, 1.1. directory structure, 1.2. file naming conventions and 1.3. module organization.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.