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/agoldian/claudenv/hypothesis-testergit clone --depth 1 https://github.com/AGoldian/claudenvWrote 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/agents/agoldian/claudenv/hypothesis-tester)<a href="https://agentmods.dev/agents/agoldian/claudenv/hypothesis-tester"><img src="https://agentmods.dev/badge/agents/agoldian/claudenv/hypothesis-tester.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 | $0.00030 | $0.00188 |
| Opus 5 | $0.00015 | $0.00094 |
| Sonnet 5 | $0.00006 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
hypothesis-tester 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 5d 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
You are testing an implementation hypothesis in an isolated git worktree.
Your workflow
- Read the parent branch context (goal, constraints, current state)
- Implement the hypothesis
- Run tests to validate
- If tests pass — commit with descriptive message, report SUCCESS
- If tests fail — report FAILURE with analysis of why, do NOT commit broken code
Output format
Report exactly one of:
HYPOTHESIS_SUCCESS: <summary of what worked and why>HYPOTHESIS_FAILURE: <summary of what failed and why>
The parent agent will decide whether to merge your worktree branch.
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.
- 5d ago First seen · 23 lines · 30 tokens per session scan A 4091510f1396
hypothesis-tester is an agent published in the GitHub repository AGoldian/claudenv (10 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 188 once invoked, about $0.0002 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
release-bundle-testing
Rozenite is a development tool. Whatever a project wires into its bundler config, a release build must ship none of our code. @rozenite/test-utils provides the bench that proves it, and every plugin owns a Vitest suite in src/tests/release-bundle.test.ts that uses it.
e2e-testing
pnpm expo run:ios pnpm expo run:android.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
playground-testing
Rozenite DevTools plugins. Every screen exists to trigger one plugin behavior; DevTools is where you observe the result.
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
worktree-collaboration
This document defines the default collaboration protocol for multiple Agents working on Vibelution in parallel.