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/adamw7/tools/testing-conventionsnpx skills add adamw7/tools --skill testing-conventionsgit clone --depth 1 https://github.com/adamw7/toolsWhat 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.00075 | $0.01181 |
| Opus 5 | $0.00037 | $0.00590 |
| Sonnet 5 | $0.00015 | $0.00236 |
| Haiku 4.5 | $0.00007 | $0.00118 |
Grade A, and why
testing-conventions 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Conventions Skill
Write unit and integration tests that satisfy the tools repo's enforced
testing rules the first time. These rules are enforced by Surefire config,
JUnit extensions, and ArchUnit architecture tests — a test that ignores them
fails the build, not just review.
Hard rules (build fails otherwise)
Timeouts
- 5 s per unit test. Surefire enforces a 5-second per-test timeout (root
pom.xml). The bound is generous because the reactor builds in parallel (-T1C) and contending test forks stretch the cold-fork warmup; it is not a budget to spend. Keep unit tests fast — no real I/O, no sleeps, no heavy loops. A genuinely heavier test opts out with an explicit@Timeoutand a comment explaining why. - Heavy shared setup (
@BeforeAlletc.) has a looser 10-second limit (15 s under coverage). A fork that hangs outright is killed at 300 s (forkedProcessTimeoutInSeconds).
Unit tests run class-parallel
- Surefire runs
unit.test.parallelism(default 3) test classes at once per module; the methods within one class still run on a single thread, so a@BeforeEach-built fixture is never shared across threads. - A
@TempDiris unique per class, so an ordinary test needs nothing extra. - Writing process-global state needs a guard, or the test corrupts whatever
runs beside it:
- a system property, or the deprecated
PathValidator.setAllowedBaseDir→ annotate the class@Isolated(org.junit.jupiter.api.parallel.Isolated); it then runs alone. ArchUnit fails the build if you forget. Confining a source with anAllowedPathsof its own writes nothing shared, and needs no annotation. - a fixture genuinely shared between classes (the embedded Derby database) →
@ResourceLock("<name>"), which serialises just those classes. Put it on the shared base class; subclasses inherit it.
- a system property, or the deprecated
- Debug a suspected ordering problem with
-Dunit.test.parallelism=1.
Network is off for unit tests
- The
datamodule'sNetworkOffExtensionengages theSwitchkill-switch before any test runs, so a unit test cannot open an outbound connection. - Anything needing the network is an integration test (
*IT), gated behind theintegration-testsprofile and run by Failsafe — not Surefire.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 94 lines · 75 tokens per session scan A 4c3ea9ccd9b8
testing-conventions is a skill published in the GitHub repository adamw7/tools (11 stars, last pushed 4d ago), licensed MIT. It adds 75 tokens to every session and 1,181 once invoked, about $0.0004 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
union-type-wrappers
Add typed getters and setters over BinaryData properties that represent TypeSpec union types in generated Java models. Use when generated classes expose BinaryData for union-typed fields and you need ergonomic, type-safe accessors instead.
build-with-tinybase
Scaffold, extend, and verify reactive local-first JavaScript or TypeScript applications with TinyBase. Use when choosing TinyBase for in-memory tabular or key-value state, generating an app with create-tinybase, adding schemas or UI bindings, configuring browser or database persistence, configuring MergeableStore…
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
run-tests
Run project tests using Maven (mvn). Use when the user asks to run tests.
search-m2
Search for Java classes inside Maven dependencies in /.m2. Use when the user asks to locate classes or inspect JARs. Cross-reference pom.xml files in the current directory to resolve dependency names/versions.
using-process-tool
Describes how to correctly use 'process' tool.