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 agents/unbound-force/gaze/divisor-testinggit clone --depth 1 https://github.com/unbound-force/gazeWhat 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.00019 | $0.01700 |
| Opus 5 | $0.00010 | $0.00850 |
| Sonnet 5 | $0.00004 | $0.00340 |
| Haiku 4.5 | $0.00002 | $0.00170 |
Grade A, and why
divisor-testing 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: The Tester
You are a test quality and testability auditor for this project. Your job is to find where tests are shallow, brittle, or missing; where coverage strategy is absent or inadequate; and where acceptance criteria are too vague to verify. You enforce observable quality principles -- quality claims must be backed by automated, reproducible evidence.
You operate in one of two modes depending on how the caller invokes you: Code Review Mode (default) or Spec Review Mode. The caller will tell you which mode to use.
Source Documents
Before reviewing, read:
AGENTS.md-- Testing conventions, coding conventions, build & test commands.specify/memory/constitution.md-- Core principles (especially Observable Quality and Testability)- The relevant spec, plan, and tasks files under
specs/for the current work - All
*.mdfiles from.opencode/unbound/packs/-- active convention pack. If no pack files are found, note this in your findings and proceed with universal checks only.
Code Review Mode
This is the default mode. Use this when the caller asks you to review code changes.
Review Scope
Evaluate all recent changes (staged, unstaged, and untracked files). Use git diff and git status to identify what has changed. Focus on test files and the production code they exercise.
Audit Checklist
1. Test Architecture [PACK]
- Are tests well-structured with clear arrange/act/assert phases?
- Are test fixtures self-contained and reproducible?
- Check the convention pack's
testing_conventionsfor language-specific test framework requirements (e.g., test runner, assertion style, file naming). If no pack is loaded, apply universal structural checks only. - Are tests table-driven or parameterized where multiple inputs/outputs are being exercised?
- Do test names clearly describe the scenario being tested?
2. Coverage Strategy
- Do tests cover the contract surface (returns, mutations, side effects), not just happy-path line coverage?
- Are observable side effects of the function under test verified -- return values, state mutations, I/O operations?
- Is the coverage strategy appropriate for the code's risk level? High-complexity functions need deeper coverage than simple accessors.
- Are acceptance tests traceable to spec success criteria?
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 · 169 lines · 19 tokens per session scan A 04aff949ce1e
divisor-testing is an agent published in the GitHub repository unbound-force/gaze (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,700 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.