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/jaycewalzer1/SilverKey-Inc.Wrote 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/jaycewalzer1/silverkey-inc./testing-tiers)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./testing-tiers"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./testing-tiers/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/jaycewalzer1/silverkey-inc./testing-tiers"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./testing-tiers.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.00000 | $0.00412 |
| Opus 5.5 | $0.00000 | $0.00165 |
| Sonnet 5.5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
testing-tiers 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.
What it actually says
Testing Tiers (Web + RN)
Goal
If tests are web-only or fragile, you’ll hesitate to refactor after cloning for RN. Enforce tests that run in shared packages and avoid patterns that block cross-platform confidence.
Rules
1. Unit tests in shared packages required
- packages/utils, packages/schemas, and other shared packages must have unit tests for non-trivial logic.
- Aim for a coverage threshold (e.g. shared packages ≥ 80% or a baseline) so refactors are safe. Configure in the test runner (e.g. Vitest
coverage.thresholds).
2. No snapshot-only tests
- Do not rely on "snapshot only" as the sole assertion. Snapshot tests are allowed only when combined with meaningful assertions (behavior or structure you care about), or use them for regression only with clear naming and review.
- Prefer testing behavior and public API over raw DOM/output snapshots so the same tests can run against RN or a different renderer later if needed.
3. No focused tests in repo
- Banned:
describe.only,it.only,test.only(or equivalent) in committed code. - Enforced by: ESLint rule
silverkey/no-focused-testsin*.test.*,*.spec.*, and__tests__/**files. - CI must run the full suite; focused tests must not be committed.
Enforcement
- ESLint:
silverkey/no-focused-tests(error) for test files. - CI: run unit tests (and coverage for shared packages when configured).
- Code review: new shared logic should have unit tests; new tests should not be snapshot-only.
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 · 38 lines · 0 tokens per session scan A 94c6cb4bec24
testing-tiers is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 412 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-08.
Other cursor rules, from other repositories
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
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.
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.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.