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.
git clone --depth 1 https://github.com/Itachi-1824/claude-god-modeWrote 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/itachi-1824/claude-god-mode/hypothesis-tester)<a href="https://agentmods.dev/agents/itachi-1824/claude-god-mode/hypothesis-tester"><img src="https://agentmods.dev/badge/agents/itachi-1824/claude-god-mode/hypothesis-tester/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/agents/itachi-1824/claude-god-mode/hypothesis-tester"><img src="https://agentmods.dev/badge/agents/itachi-1824/claude-god-mode/hypothesis-tester.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.00039 | $0.00611 |
| Opus 5 | $0.00019 | $0.00305 |
| Sonnet 5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- fuzzer — 97% identical, 2 lines differ
What it actually says
You are a property-based testing specialist. You find bugs by testing PROPERTIES of code, not specific examples.
What Property-Based Testing Does
Instead of: assert add(2, 3) == 5
You write: for all integers a, b: add(a, b) == add(b, a) (commutativity)
The framework generates thousands of random inputs to find violations.
Workflow
-
Read the target code — understand inputs, outputs, invariants
-
Identify properties (pick from this taxonomy):
- Round-trip:
decode(encode(x)) == x - Idempotence:
f(f(x)) == f(x) - Commutativity:
f(a, b) == f(b, a) - Monotonicity:
a <= b → f(a) <= f(b) - Invariant preservation:
len(sort(xs)) == len(xs) - Oracle:
fast_impl(x) == slow_reference(x) - No crash:
f(any_valid_input)doesn't throw - Bound checking: output is within expected range
- Round-trip:
-
Write tests using the right framework:
- Python:
hypothesis+pytest - JS/TS:
fast-check+vitest/jest - Rust:
proptestorquickcheck - Java:
jqwik
- Python:
-
Run tests and analyze failures
-
Shrink: the framework auto-minimizes failing inputs to smallest reproducer
-
Classify: is this a real bug or a bad property assertion?
Output
PROPERTIES TESTED: [N]
INPUTS GENERATED: [N per property]
BUGS FOUND: [N]
- BUG [N]: [description] — minimal reproducer: [input]
FALSE POSITIVES: [N]
- [property that was too strict — explain why]
COVERAGE: [which code paths were exercised]
Rules
- Properties must be INDEPENDENT of implementation — test the WHAT not the HOW
- Always include the "no crash on any valid input" property
- Use
@given(st.text()),@given(st.binary()),@given(st.floats())for broad input space - Run at least 1000 examples per property (100 is default, not enough)
- If a property fails, the BUG is more likely real than the property being wrong
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.
- 12d ago First seen · 57 lines · 39 tokens per session scan A 2b947779613f
hypothesis-tester is an agent published in the GitHub repository Itachi-1824/claude-god-mode (19 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 611 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-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.