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/caliber-ai-org/ai-setup/testinggit clone --depth 1 https://github.com/caliber-ai-org/ai-setupWhat 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.00194 |
| Opus 5 | $0.00000 | $0.00097 |
| Sonnet 5 | $0.00000 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
testing scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Use `vi.mock()` for `fs`, `child_process` · `vi.mocked()` for type-safe assertions What it actually says
- Vitest config:
vitest.config.ts· Setup:src/test/setup.ts - Run all:
npm run test· Single:npx vitest run src/scoring/__tests__/accuracy.test.ts - Coverage:
npm run test:coverage(v8 provider) - LLM calls globally mocked in
src/test/setup.ts— never call real providers - Use
vi.mock()forfs,child_process·vi.mocked()for type-safe assertions - Tests colocated:
src/llm/__tests__/config.test.tstestssrc/llm/config.ts - Pattern:
describe→beforeEach(vi.clearAllMocks)→itwithexpect - Environment vars: save in
beforeEach, restore inafterEach
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 · 13 lines · 0 tokens per session scan A 2f657a75c504
testing is a cursor rule published in the GitHub repository caliber-ai-org/ai-setup (1,255 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 194 tokens. A static security scan graded it A with 1 finding (runs shell commands). 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
ui
React components must be functional and prop-typed.
cursorrules
DeepInit projection provenance (R3) stage: EMIT → PROJECT (cursor) runid: run-2026-06-13-kemal-e2e source: AGENTS.md (lean tier) — deterministic projection, no new findings note: content inside the DEEPINIT markers is owned + regenerated; edit OUTSIDE them. -->.
cursorrules
Cursor rule "cursorrules" from syf2211/ruledoctor, covering 订单服务项目规则（demo） and 硬性规则.
cursorrules
All agent instructions live in AGENTS.md (single source of truth). Do not add rules here.
integrations
External integration rules — providers, idempotency, bulkhead, observability.
main
Core coding standards enforced on all source files.