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/jabrena/jbang-mcp-examplesWrote 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/jabrena/jbang-mcp-examples/202-book-pragmatic-unit-testing)<a href="https://agentmods.dev/rules/jabrena/jbang-mcp-examples/202-book-pragmatic-unit-testing"><img src="https://agentmods.dev/badge/rules/jabrena/jbang-mcp-examples/202-book-pragmatic-unit-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/jabrena/jbang-mcp-examples/202-book-pragmatic-unit-testing"><img src="https://agentmods.dev/badge/rules/jabrena/jbang-mcp-examples/202-book-pragmatic-unit-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.00339 | $0.00339 |
| Opus 5 | $0.00169 | $0.00169 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
202-book-pragmatic-unit-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 10d 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
Pragmatic Unit Testing: Summary
General Principles:
- Test anything that might break Test everything that does break
- New code is guilty until proven innocent Write at least as much test code as production code
- Run local tests with each compile
- Run all tests before check-in to repository
Questions to Ask:
- If the code ran correctly, how would I know?
- How am I going to test this? What else can go wrong? Could this same kind of problem happen anywhere else?
- What to Test: Use Your RIGHT-BICEP Are the results right?
- Are all the boundary conditions CORRECT? Can you check inverse relationships?
- Can you cross-check results using other means?
- Can you force error conditions to happen? Are performance characteristics within bounds?
Good tests are A TRIP
- Automatic
- Thorough
- Repeatable
- Independent Professional
- Conformance
CORRECT Boundary Conditions
- Does the value conform to an expected format?
- Ordering — Is the set of values ordered or unordered as appropriate?
- Range — Is the value within reasonable minimum and maximum values?
- Reference - Does the code reference anything external that isn't under direct control of the code itself?
- Existence - Does the value exist? (e.g., is non-null, non-zero, present in a set, etc.)
- Cardinality - Are there exactly enough values?
- Time (absolute and relative) - Is everything happening in order? At the right time? In time?
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.
- 10d ago First seen · 38 lines · 339 tokens per session scan A 4836b8c602f9
202-book-pragmatic-unit-testing is a cursor rule published in the GitHub repository jabrena/jbang-mcp-examples (1 stars, last pushed 1y ago), licensed Apache-2.0. It adds 339 tokens to every session, about $0.0017 per session on Opus 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
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
mockito
This guide provides definitive best practices for writing robust, maintainable, and readable unit tests using Mockito with JUnit 5, focusing on modern patterns and common pitfalls.
python-general-coding-standards
A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.
spec-for-ut
Unit testing is essential to ensure the reliability and stability of code, especially for React components and functions. Adhering to best practices and ensuring high test coverage is critical to maintaining a robust codebase.
unit-testing-standards
Cursor rule "unit-testing-standards" from adobecom/da-express-milo, covering unit testing standards, testing philosophy, testing framework stack, test structure patterns and 1. standard test file organization.
project-conventions
Core project conventions for the Uniqlo Sales Alerter.