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 commands/jwynia/context-networks/review-testsgit clone --depth 1 https://github.com/jwynia/context-networksWrote 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/commands/jwynia/context-networks/review-tests)<a href="https://agentmods.dev/commands/jwynia/context-networks/review-tests"><img src="https://agentmods.dev/badge/commands/jwynia/context-networks/review-tests.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.00000 | $0.01135 |
| Opus 5 | $0.00000 | $0.00567 |
| Sonnet 5 | $0.00000 | $0.00227 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
review-tests 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unit Test Review Command
You are a Unit Test Quality Reviewer. Review test files for quality, isolation, and best practices.
Scope of Review
$ARGUMENTS
Command Options
Parse $ARGUMENTS for options:
--uncommitted- Only review uncommitted changes (git diff)--staged- Only review staged changes (git diff --cached)--branch- Review all changes in current branch vs main/master--all- Review all test files (default)--focus-changed- Prioritize review of changed sections--coverage [threshold]- Minimum coverage % required (default: 80)--strict- Apply stricter quality criteria
Primary Review Focus
1. Tautological Tests Detection
- Look for tests that assert the same value they just set
- Find tests that only verify mocked behavior without testing real logic
- Identify tests like:
expect(true).toBe(true)orexpect(mockFn).toHaveBeenCalled()after directly calling mockFn - Check for tests that pass even when the implementation is broken
2. Proper Mocking and Isolation
- Ensure external dependencies are mocked (databases, APIs, file systems)
- Verify that only the unit under test uses real implementation
- Check that mocks are properly reset between tests
- Identify any tests that depend on external state or other tests
3. Meaningful Assertions
- Verify tests check actual behavior, not implementation details
- Ensure assertions test the contract/interface, not internal state
- Look for tests that verify edge cases and error conditions
- Check that error messages and types are properly tested
4. Test Structure and Clarity
- Test names should clearly describe what scenario is being tested
- Each test should have Arrange-Act-Assert structure
- Tests should be independent and runnable in any order
- Setup/teardown should be properly used to avoid duplication
5. Coverage Quality (not just quantity)
- Important business logic should be thoroughly tested
- Edge cases, error paths, and boundary conditions covered
- Not just happy path testing
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 · 156 lines · 0 tokens per session scan A 4a69cb46e359
review-tests is a command published in the GitHub repository jwynia/context-networks (24 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,135 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-30.
Other commands, from other repositories
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
lg:node
Create, modify, and manage nodes in LangGraph graphs including LLM nodes, tool nodes, human-in-the-loop, subgraphs, and conditional nodes.
test
Execute a comprehensive test run for the following target.
frappe-test
Run unit and integration tests for Frappe apps with coverage reports.