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.
npx agentmods add rules/pallerana/agentic-loop-engineering-kit/jabrena-302-java-testing-fundamentalsgit clone --depth 1 https://github.com/pallerana/agentic-loop-engineering-kitWhat 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 | $0.00000 | $0.00253 |
| Opus 5 | $0.00000 | $0.00127 |
| Sonnet 5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
jabrena-302-java-testing-fundamentals 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 2d 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
Java testing fundamentals (external cherry-pick)
Source: jabrena/cursor-rules-java rule 302 — adapted for your monorepo.
Naming
methodUnderTest_stateUnderTest_expectedBehavior- Example:
getOrder_whenNotFound_returns404
Structure
- Arrange / Act / Assert — blank line between sections.
- One logical behavior per test method.
- Use
@ParameterizedTestfor input variants (null, empty, boundary).
Assertions
- Prefer AssertJ (
assertThat) over JUnit legacy asserts. - Assert exceptions with
assertThatThrownByorassertThrows. - No test logic in production code (
if (isTest)forbidden).
Agent loop
- Every Copilot/CodeQL fix cites a named test in the PR thread reply.
- Test matrix IDs (Phase 1) should map to test method names in close-the-loop Jira comment.
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.
- 2d ago First seen · 34 lines · 253 tokens per session scan A 64c97c7bd82a
jabrena-302-java-testing-fundamentals is a cursor rule published in the GitHub repository pallerana/agentic-loop-engineering-kit (4 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 253 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.