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/vlad-ryzhkov/AI-QA-workshop-feb19Wrote 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/vlad-ryzhkov/ai-qa-workshop-feb19/03-skill-testcases)<a href="https://agentmods.dev/rules/vlad-ryzhkov/ai-qa-workshop-feb19/03-skill-testcases"><img src="https://agentmods.dev/badge/rules/vlad-ryzhkov/ai-qa-workshop-feb19/03-skill-testcases/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/vlad-ryzhkov/ai-qa-workshop-feb19/03-skill-testcases"><img src="https://agentmods.dev/badge/rules/vlad-ryzhkov/ai-qa-workshop-feb19/03-skill-testcases.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.00116 |
| Opus 5.5 | $0.00000 | $0.00046 |
| Sonnet 5.5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
03-skill-testcases 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 2mo 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
SKILL: TEST CASES
TRIGGER
Use this when generating test scenarios matrix from API specification.
LOGIC SOURCE
EXECUTE the instruction set defined in: .claude/skills/test-cases/SKILL.md
@.claude/skills/test-cases/SKILL.md
OUTPUT
Output: audit/test-scenarios.md
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.
- 2mo ago First seen · 18 lines · 116 tokens per session scan A 39a93bca7770
03-skill-testcases is a cursor rule published in the GitHub repository vlad-ryzhkov/AI-QA-workshop-feb19 (26 stars, last pushed 7mo ago), licensed Unlicense. It costs nothing until one of its globs matches a file; then it loads 116 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
cursor-rule-example
SKILL: Generate Ktor/JUnit API Tests (use for /api-tests).
telegram-bot-tests
Test conventions for Telegram Bot library.
standard-backend-tests-redaction
This standard establishes best practices for writing backend tests using Jest in the Packmind monorepo. It focuses on clarity, maintainability, and consistency across test suites by emphasizing behavi... .
standard-integration-tests-structure-and-patterns
Define testing patterns for integration tests in the Packmind monorepo to ensure consistent organization, proper resource management, and comprehensive test coverage using hexagonal architecture princ... .
standard-e2e-writing-e2e-tests
Writing proper E2E tests with our stack. Each feature we add should have its own spec file. .
fix-bug
Fix a bug using the knowledge layer — reproduce first, failing regression test, root cause, surgical fix, review and ledger entry after.