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/openshift/rosaWrote 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/openshift/rosa/20-testing-generated-and-structure)<a href="https://agentmods.dev/rules/openshift/rosa/20-testing-generated-and-structure"><img src="https://agentmods.dev/badge/rules/openshift/rosa/20-testing-generated-and-structure/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/openshift/rosa/20-testing-generated-and-structure"><img src="https://agentmods.dev/badge/rules/openshift/rosa/20-testing-generated-and-structure.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.00212 |
| Opus 5.5 | $0.00000 | $0.00085 |
| Sonnet 5.5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
20-testing-generated-and-structure 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, Generated Files, And Structure
- Use Ginkgo v2 and Gomega in the style already used by the surrounding package.
- Do not weaken existing assertions just to make a new change pass.
- Add focused coverage for behavior changes, especially new flags, branching logic, and error paths.
- Prefer nearby helpers and suite patterns over inventing a new test harness.
- Generated mocks come from
make generate; do not edit files underpkg/*/mocks/orcmd/create/idp/mocks/by hand. - If command or flag behavior changes, verify the structure-test YAML files stay aligned even if the edited file is not a test file.
- If CLI help or command docs change, remember
make generate-docsmay be part of verification.
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 · 20 lines · 0 tokens per session scan A d2986d90ee0e
20-testing-generated-and-structure is a cursor rule published in the GitHub repository openshift/rosa (103 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 212 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
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
go
Idiomatic Go rules. Explicit error handling, interface-based design, context-first concurrency.
code_standards
Spamoor Code Standards and Conventions.
development_workflow
Spamoor Development Workflow and Best Practices.
schema_test_implementation_guide
A concise and practical guide for building GoZod Schema test files, updated with the latest practices from stringtest.go, objecttest.go, and complextest.go.
checks_implementation_guide
This document provides implementation guidelines for GoZod validation checks based on the current architecture. All checks follow a unified factory function pattern that directly creates core.ZodCheckInternals instances with optional JSON Schema support.