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 skills/rocky2431/ultra-builder-pro/testing-rulesnpx skills add rocky2431/ultra-builder-pro --skill testing-rulesgit clone --depth 1 https://github.com/rocky2431/ultra-builder-proWrote 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/skills/rocky2431/ultra-builder-pro/testing-rules)<a href="https://agentmods.dev/skills/rocky2431/ultra-builder-pro/testing-rules"><img src="https://agentmods.dev/badge/skills/rocky2431/ultra-builder-pro/testing-rules.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.00010 | $0.00425 |
| Opus 5 | $0.00005 | $0.00212 |
| Sonnet 5 | $0.00002 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
testing-rules 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 6d 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 Rules
These rules are mandatory for all test-related work.
TDD Workflow
RED → GREEN → REFACTOR (all new code).
Test Strategy
| Layer | Test Type | Mock Strategy |
|---|---|---|
| Functional Core | Unit Test | No mocks needed (pure input→output) |
| Imperative Shell | Integration | Testcontainers (real DB/services) |
| External APIs | Test Double | With // Test Double rationale: [reason] |
Forbidden Patterns
These patterns are never acceptable:
| Pattern | Why Forbidden | Alternative |
|---|---|---|
jest.fn() for Repository/Service/Domain |
Invalid test — doesn't prove production works | Testcontainers |
class InMemoryRepository |
Diverges from real DB behavior | Real DB container |
class MockXxx / class FakeXxx |
Hides integration issues | Direct instantiation or Testcontainers |
jest.mock('../services/X') |
Skips real collaboration | Test real collaboration |
it.skip('...database...') |
"Too slow" is not valid | Testcontainers are fast enough |
Coverage Requirements
- 80% overall minimum
- 100% Functional Core (pure logic must be fully tested)
- Critical paths for Imperative Shell
Dev/Prod Parity
Tests must use real dependencies:
- Real database via Testcontainers (not in-memory substitutes)
- Config via environment variables
- Mock tests passing ≠ production working
Detection Checklist
When analyzing test files, flag:
- Any
jest.fn()usage on Repository, Service, or Domain classes - Any
InMemory*orMock*orFake*class definitions - Any
jest.mock()calls on internal modules - Any skipped tests with database/slow excuses
- Missing error case coverage
- Missing edge case coverage
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.
- 6d ago First seen · 57 lines · 10 tokens per session scan A b042a1920f0c
testing-rules is a skill published in the GitHub repository rocky2431/ultra-builder-pro (11 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 425 once invoked, about $0.0001 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-30.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
nw-ddd-eventsourcing
Event Sourcing and CQRS as DDD implementation patterns — when to use, aggregate event streams, projections, snapshots, sagas, upcasting, conflict resolution.
nw-diverge
Generates 3-5 divergent design directions through JTBD analysis, competitive research, structured brainstorming, and taste evaluation before convergence. Use when the team has a validated problem but hasn't chosen a solution approach.