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.
git clone --depth 1 https://github.com/kznr02/OpenTester-SkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/kznr02/opentester-skills/opentester)<a href="https://agentmods.dev/rules/kznr02/opentester-skills/opentester"><img src="https://agentmods.dev/badge/rules/kznr02/opentester-skills/opentester/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/kznr02/opentester-skills/opentester"><img src="https://agentmods.dev/badge/rules/kznr02/opentester-skills/opentester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.01172 | $0.01172 |
| Opus 5.5 | $0.00469 | $0.00469 |
| Sonnet 5.5 | $0.00234 | $0.00234 |
| Haiku 4.5 | $0.00117 | $0.00117 |
Grade A, and why
opentester 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenTester Testing Guidelines
When to Use
When the user mentions:
- "/test" or "/t" - Create tests for code changes
- "run tests" - Execute existing tests
- "validate" - Check test syntax
- "delete project" or "delete test" - Remove test data
- Test files are modified
DSL Validation Workflow (CRITICAL)
ALWAYS validate DSL before saving!
1. Generate DSL YAML
2. Call opentester.validateDSL(dsl_yaml) to check syntax
3. IF validation fails:
- Read the error message
- Fix the DSL (common: use assertion object instead of direct type/value)
- Call validateDSL again
- REPEAT until validation passes
4. IF validation passes:
- Call opentester.saveCase to store the test
5. Call opentester.runCase to execute
DSL Format
Basic Structure
version: "1.0"
meta:
name: "Test Name"
description: "What this test verifies"
target:
type: cli # cli, api, or tui
timeout: 10
steps:
- name: "Step description"
action: exec|assert|wait
# action-specific fields
Action: exec
- name: "Execute command"
action: exec
command: "echo Hello" # CLI
# OR for API:
method: GET
path: "/endpoint"
Action: assert (CRITICAL - USE assertion OBJECT!)
❌ WRONG - assert with direct type/value:
- action: assert
type: stdout_contains # ❌ Wrong!
value: "text" # ❌ Wrong!
✅ CORRECT - assert with assertion object:
- name: "Verify output"
action: assert
assertion: # ✅ Correct!
type: stdout_contains
expected: "text" # ✅ Use 'expected', not 'value'!
CLI Assertions:
- action: assert
assertion:
type: exit_code|stdout_contains|stderr_contains|stdout_matches|stderr_empty
expected: value
API Assertions:
- action: assert
assertion:
type: status_code|json_path
path: "$.data.name" # Required for json_path
expected: value
TUI Assertions:
- action: assert
assertion:
type: screen_contains|cursor_at|screen_stable
expected: value
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.
- 1mo ago First seen · 177 lines · 1,172 tokens per session scan A 448dd98cbb5f
opentester is a cursor rule published in the GitHub repository kznr02/OpenTester-Skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 1,172 tokens to every session, about $0.0047 per session on Opus 5.5. 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-31.
Other cursor rules, from other repositories
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.