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/omergulcicek/omergulcicek.com/testinggit clone --depth 1 https://github.com/omergulcicek/omergulcicek.comWhat 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.00215 |
| Opus 5 | $0.00000 | $0.00108 |
| Sonnet 5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00021 |
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 Guide (Pragmatic)
Principles
- Value over Coverage: Focus on testing complex business logic in
features/[feature]. Skip simple UI components unless critical. - Behavior Testing: Focus on user outcomes (Arrange-Act-Assert).
Tech Stack
- Vitest & React Testing Library.
Preferences (Not Hard Rules)
- API: Use
MSWfor stable features; simple mocks are okay for rapid prototyping. - Location: Keep
.test.tsnext to implementation. - Snapshots: Use only for small, static data structures to prevent maintenance hell.
Correct Approach
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 · 27 lines · 0 tokens per session scan A 70d2942972d0
testing is a cursor rule published in the GitHub repository omergulcicek/omergulcicek.com (15 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 215 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-09-01.
Other cursor rules, from other repositories
unit-tests-tdd
TDD required for behavior changes; ≥80% package coverage on touched packages; unit-test conventions.
commit-checks
Run gofmt, go vet, and unit tests before committing Go files.
unit-testing
Python integration and unit testing — pytest patterns, test classes, workflow test tips.
testing
Testing conventions and Playwright patterns.
unit-testing-standards
Cursor rule "unit-testing-standards" from adobecom/da-express-milo, covering unit testing standards, testing philosophy, testing framework stack, test structure patterns and 1. standard test file organization.
testing
Guide for writing pytest unit and integration tests.