Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dayvisonassis/sdd-skillsnpx agentmods add skills/dayvisonassis/sdd-skills/monorepo-unit-test-validatorWrote 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/dayvisonassis/sdd-skills/monorepo-unit-test-validator)<a href="https://agentmods.dev/skills/dayvisonassis/sdd-skills/monorepo-unit-test-validator"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/monorepo-unit-test-validator/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/skills/dayvisonassis/sdd-skills/monorepo-unit-test-validator"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/monorepo-unit-test-validator.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.00112 | $0.01139 |
| Opus 5 | $0.00056 | $0.00570 |
| Sonnet 5 | $0.00022 | $0.00228 |
| Haiku 4.5 | $0.00011 | $0.00114 |
Grade A, and why
monorepo-unit-test-validator 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepo Unit Test Validator (PABX)
Audit unit test files across the PABX monorepo (excluding backend/frontend) to ensure they
comply with every rule the monorepo-unit-test-writer enforces. Read-only: produce a
compliance report; never modify test/production files, never execute tests (static analysis only).
Project scope: PABX monorepo apps (not backend/frontend). The full rule set is in
../monorepo-unit-test-writer/references/pabx-rules.md— validate against it.
Scope: any apps/{app} except backend/frontend. Stacks: node-express, node-worker, python-fastapi.
INPUT
test_file_path(required) andapp_name(required).checklist_file_path(optional) — the.unit-test.mdfor coverage cross-reference.target_file(optional) — the source under test.severity_filter(optional) —critical|major|minor(default: all).
OUTPUT
A compliance report (English): summary counts, detected stack, applicable rule categories,
overall verdict (PASS = 0 critical + 0 major; PASS WITH WARNINGS = 0 critical, some
major/minor; FAIL = ≥1 critical), each violation ([SEVERITY] Rule-ID, stack, location,
description, expected, found, fix), coverage/performance analysis, and positive findings. When
dispatched by the evaluator, the verdict is the signal it consumes.
EXECUTION STEPS (3 Phases)
Phase 1 — Structural Analysis
Detect the stack (node-express / node-worker / python-fastapi). Inventory test blocks
(Node: describe/it/hooks/helpers; Python: class Test*/def test_*/fixtures/conftest.py).
Map checklist ↔ tests and source ↔ tests (if provided). Note imports and mock-vs-import order
(Node jest.mock(); Python sys.modules patching). Identify mocks and cleanup points.
Phase 2 — Rule-by-Rule Validation
Check EVERY applicable rule from ../monorepo-unit-test-writer/references/pabx-rules.md:
- Language & Naming [Common, CRITICAL] · Test Structure [Common, MAJOR] · Mock & Isolation [Common, CRITICAL].
- Node common [NE+NW, CRITICAL] —
importnotrequire;jest.mock()before import;jest.clearAllMocks();.test.ts; location mirrors source. - Node Express [NE, CRITICAL] — controller
req/res/next; service mocks; model Promise.all() (new mock per call,.thenbind,clone()new); routes excluded; middlewarenext()flow. - Node Worker [NW, CRITICAL] — connections mocked (DB/Redis/BullMQ/Qdrant/Neo4j); AGI session mock; dbevents source mock; job payload valid+invalid; graceful shutdown; pipeline isolation.
- Python FastAPI [PF, CRITICAL] — GPU/ML mocked before imports;
TestClient; no real model loading;@pytest.mark.asyncio;conftest.py; correct@patchtarget; no hardcoded paths. - Coverage [Common, MAJOR] · Forbidden Practices [Common, CRITICAL] · Resource Cleanup [Common, MAJOR] (incl. Python fixture scoping).
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 · 75 lines · 112 tokens per session scan A a725d713e7ea
monorepo-unit-test-validator is a skill published in the GitHub repository dayvisonassis/sdd-skills (1 stars, last pushed 13d ago), licensed MIT. It adds 112 tokens to every session and 1,139 once invoked, about $0.0006 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 skills, from other repositories
review-ugc-render
Mandatory pre-publish review gate for a UGC video render. Transcribes the finished render's AUDIO with Whisper and word-diffs it against the approved spoken script, then gates setfinalrender — blocking a render whose generated audio mis-voices a word (e.g. the approved "human-vetted" spoken as "human witted"), drops…
test-generator
A test-writing helper that creates unit or integration tests from the code's actual behavior and contracts. Unit tests check small pieces of code, while integration tests check how real components work together.
testing-r-packages
Best practices for writing R package tests using testthat version 3+. Use when writing, organizing, or improving tests for R packages. Covers test structure, expectations, fixtures, snapshots, mocking, and modern testthat 3 patterns including self-sufficient tests, proper cleanup with withr, and snapshot testing.
r-package-development
R package development with devtools, testthat, and roxygen2. Use when the user is working on an R package, running tests, writing documentation, or building package infrastructure.
111-java-maven-dependencies
Use when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a…
130-java-testing-strategies
Use when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions. This should trigger for requests such as Review Java code for testing strategies; Apply RIGHT-BICEP testing strategies in Java code…