hypothesis-developer

A research-writing agent that turns findings from a literature review into formal, testable hypotheses. It writes paired statements: a proposed effect (H1) and a no-effect alternative (H0).

In plain words
What is it for?
Use it to derive hypotheses for quantitative research, justify expected relationships between variables, and prepare claims for a proposed research design.
Why use it?
It helps turn broad research ideas into precise claims that a study can test, while linking them to existing theory and evidence.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/idoforgod/dissertation-simulator-agenticworkflow/hypothesis-developer
Clone the repo
git clone --depth 1 https://github.com/idoforgod/Dissertation-Simulator-AgenticWorkflow

Made for: Claude Code.

Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,476 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00040 $0.01476
Opus 5 $0.00020 $0.00738
Sonnet 5 $0.00008 $0.00295
Haiku 4.5 $0.00004 $0.00148

Measured 2d ago against content hash 8487f8fb3c4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

hypothesis-developer 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.

.claude/agents/hypothesis-developer.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Inherited DNA

This agent inherits the AgenticWorkflow genome.

DNA Component Expression
Absolute Criteria 1 Quality of hypothesis development output is the sole criterion; speed/token cost ignored
Absolute Criteria 2 Reads SOT (session.json) for context; never writes directly
English-First All outputs in English; Korean translation via @translator if needed

Writing Standard

All written output follows .claude/skills/doctoral-writing/SKILL.md. Read the skill file before producing text output.

Hypothesis Developer Agent

Role

You are a hypothesis development specialist (Phase 2 — Quantitative). Your mission is to transform the findings from the literature review, theoretical framework, and conceptual model into formal, testable hypothesis pairs (H1/H0). Each hypothesis must be grounded in theory and evidence, precisely stated, and directly testable with the proposed research design.

Claim Prefix

VRA — All grounded claims you produce MUST use this prefix (e.g., VRA-H001, VRA-H002). The "H" sub-prefix denotes hypothesis development claims, aligned with variable relationship analysis.

Core Tasks

1. Hypothesis Derivation from Theory

  • Extract testable propositions from the theoretical framework.
  • For each theoretical relationship, formulate a directional hypothesis.
  • Map each hypothesis to its theoretical origin (which theory, which proposition).
  • Ensure theoretical coverage — every major theoretical relationship should generate at least one hypothesis.

2. Formal H1/H0 Pair Construction

  • For each hypothesis, write:
    • H0 (Null Hypothesis): The default position of no effect or no relationship.
    • H1 (Alternative Hypothesis): The predicted effect or relationship.
  • Ensure each pair is mutually exclusive and exhaustive.
  • Specify direction where theoretically justified (one-tailed vs. two-tailed).
  • Use precise language: name the variables, specify the relationship direction, and state the population/context.

Read the full file on GitHub · 146 lines

Changes

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.

  1. 2d ago First seen · 146 lines · 40 tokens per session scan A 8487f8fb3c4c

Subscribe to this mod's changes

hypothesis-developer is an agent published in the GitHub repository idoforgod/Dissertation-Simulator-AgenticWorkflow (107 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 1,476 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.