awesome-cursor-rules-mdc is a generator that creates Cursor MDC rule files from structured library information, using semantic search and language models to gather and organize guidance. Developers use it to produce reusable rules for libraries in Cursor, and the catalogue includes 200 of those rules.
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/sanjeed5/awesome-cursor-rules-mdcWrote 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/sanjeed5/awesome-cursor-rules-mdc/junit)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/junit"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/junit.svg" alt="Measured on agentmods" 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.03171 | $0.03171 |
| Opus 5 | $0.01586 | $0.01586 |
| Sonnet 5 | $0.00634 | $0.00634 |
| Haiku 4.5 | $0.00317 | $0.00317 |
Grade A, and why
junit 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 3d 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 — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
junit Best Practices
JUnit 5 (Jupiter) is the bedrock of modern Java unit testing. This guide outlines the essential practices for crafting robust, readable, and reliable tests that integrate seamlessly into your development workflow. Adhere to these rules to ensure your tests are a valuable asset, not a burden.
1. Code Organization and Structure
1.1. Test File and Package Naming
Always mirror your production code's package structure within src/test/java. Name test classes by appending Test to the class they verify.
❌ BAD:
// src/test/java/com/example/UserServiceLogic.java
package com.example;
class UserServiceLogic { /* ... */ }
✅ GOOD:
// src/main/java/com/example/UserService.java
package com.example;
class UserService { /* ... */ }
// src/test/java/com/example/UserServiceTest.java
package com.example;
class UserServiceTest { /* ... */ }
1.2. Descriptive Test Method Naming
Test method names must clearly convey their purpose: the scenario being tested, the action, and the expected outcome. Use the Given_When_Then pattern or methodName_condition_expectedResult. For enhanced readability in test reports, leverage @DisplayName.
❌ BAD:
@Test
void testAdd() { /* ... */ }
@Test
void calculateDiscount() { /* ... */ }
✅ GOOD:
import org.junit.jupiter.api.DisplayName;
import org.junit.jupiter.api.Test;
class CalculatorTest {
@Test
@DisplayName("Given two positive numbers, when added, then return their sum")
void add_TwoPositiveNumbers_ReturnsSum() {
// Arrange, Act, Assert
}
@Test
void calculateDiscount_PremiumCustomer_Applies20PercentDiscount() {
// Arrange, Act, Assert
}
}
1.3. Logical Grouping with @Nested
For complex classes with many behaviors, use @Nested classes to group related tests. This improves readability and organization, especially when dealing with different states or conditions.
❌ BAD:
class OrderServiceTest {
@Test void createOrder_ValidInput_ReturnsOrder() { /* ... */ }
@Test void createOrder_InvalidProduct_ThrowsException() { /* ... */ }
@Test void cancelOrder_ExistingOrder_SetsStatusToCancelled() { /* ... */ }
@Test void cancelOrder_NonExistingOrder_ThrowsException() { /* ... */ }
}
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.
- 3d ago First seen · 464 lines · 3,171 tokens per session scan A ca17006e1e9a
junit is a cursor rule published in the GitHub repository sanjeed5/awesome-cursor-rules-mdc (3,571 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 3,171 tokens to every session, about $0.0159 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-09-03.
Other cursor rules, from other repositories
spring-testing
Spring Boot testing standards for unit and integration tests with Testcontainers.
java-testing
Cursor rule "java-testing" from EarthChen/ai-assets, covering java testing, test framework, test organization, unit test pattern and parameterized tests.
java-testing
A specification for generating unit tests for the Repository layer of Spring Boot applications. A repository is the code that reads and writes application data, and Spring Boot is a Java framework for building such applications.
121-java-unit-testing
Java Unit testing guidelines.
go
Idiomatic Go rules. Explicit error handling, interface-based design, context-first concurrency.
mocking-dependencies-in-tests
Cursor rule "mocking-dependencies-in-tests" from PaulJPhilp/EffectPatterns, covering mocking dependencies in tests and example.