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/RedHatProductSecurity/osidbWrote 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/redhatproductsecurity/osidb/testing)<a href="https://agentmods.dev/rules/redhatproductsecurity/osidb/testing"><img src="https://agentmods.dev/badge/rules/redhatproductsecurity/osidb/testing/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/redhatproductsecurity/osidb/testing"><img src="https://agentmods.dev/badge/rules/redhatproductsecurity/osidb/testing.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.00696 | $0.00696 |
| Opus 5.5 | $0.00278 | $0.00278 |
| Sonnet 5.5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00070 | $0.00070 |
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 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running Tests in OSIDB
OSIDB uses tox inside a testrunner container (podman). Most tests require a running database and/or web server, so the general path is via podman exec into the testrunner container.
Quick Reference
| Scenario | Command |
|---|---|
| Pure unit tests (no DB/server) | tox -e unit-tests -- path/to/test.py::TestClass |
| Everything else (general path) | podman exec -it testrunner tox -e tests -- path/to/test.py::TestClass |
| All tests | make testrunner.all-tests |
Running a Specific Test
For most tests (integration, endpoint, anything needing DB or web server):
podman exec -it testrunner tox -e tests -- osidb/tests/test_foo.py::TestClass
podman exec -it testrunner tox -e tests -- osidb/tests/test_foo.py::TestClass::test_method
For pure unit tests that have no DB or web server dependency, tox can be run locally:
tox -e unit-tests -- osidb/tests/test_foo.py::TestClass
make testrunner Entrypoints
Run these from the repo root (they all exec into the testrunner container):
| Target | What it runs |
|---|---|
make testrunner |
make checkin (lint + typecheck + unit tests) |
make testrunner.all-tests |
Full test suite (tox -e tests) |
make testrunner.all-unit-tests |
All unit tests across modules |
make testrunner.all-integration-tests |
Integration tests only |
make testrunner.osidb |
Unit tests for osidb/ |
make testrunner.bzimport |
Unit tests for collectors/bzimport |
make testrunner.jiraffe |
Unit tests for collectors/jiraffe |
make testrunner.workflows |
Unit tests for apps/workflows |
make testrunner.sla |
Unit tests for apps/sla |
make testrunner.lint |
Linting only |
make testrunner.typecheck |
Type checking only |
make testrunner.rls |
Row-level security tests |
Tox Environments
tests— full suite (unit + integration; requires DB and web server)unit-tests— unit tests only (no DB/server required)integration-tests— integration tests onlyrecord-new/record-rewrite— record VCR cassettes for network tests
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 · 69 lines · 696 tokens per session scan A 56ecd653f165
testing is a cursor rule published in the GitHub repository RedHatProductSecurity/osidb (46 stars, last pushed yesterday), licensed MIT. It adds 696 tokens to every session, about $0.0028 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-30.
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.
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.