vedix-hypothesizer

A research-planning agent that turns an idea and existing literature into a testable hypothesis, mathematical models, statistical methods, and a plan for connecting the work to code.

In plain words
What is it for?
Use it to prepare hypothesis.md and equations.txt for experiments in areas such as machine learning, optimization, statistics, mathematics, computational biology, or software engineering.
Why use it?
It helps turn a broad research idea into something that can be tested and compared with earlier work. It also checks stored prior hypotheses and known failure patterns for relevant guidance.

Agent

Part of the vedix plugin — 1 skill, 6 commands, 17 agents, 4 hooks, 10 MCP servers shipped together

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/danilkotelnikov/vedix/hypothesizer
Clone the repo
git clone --depth 1 https://github.com/danilkotelnikov/vedix

Or install vedix, the plugin that ships this one along with the rest of its 1 skill, 6 commands, 17 agents, 4 hooks, 10 MCP servers.

Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 775 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.00036 $0.00775
Opus 5 $0.00018 $0.00387
Sonnet 5 $0.00007 $0.00155
Haiku 4.5 $0.00004 $0.00077

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

Security

Grade A, and why

vedix-hypothesizer 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.

plugins/vedix/agents/hypothesizer.md · 96 lines

How it starts

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

Hypothesizer

Generate hypothesis.md and equations.txt from literature + idea + prior knowledge.

Inputs

  • <input name="topic">, <input name="domain">
  • <input name="idea_json"> — from ideator
  • <input name="paper_list_compact"> — first 10 papers (title, first author, year, abstract snippet)
  • <input name="codebase_analysis"> — if present
  • <input name="prior_hypotheses"> — search results from mcp__vedix__search_knowledge_index(query=topic, mem_type="hypotheses")
  • <input name="prior_failures"> — failure patterns from get_meta_analysis()
  • <input name="interactivity">

Steps

  1. Recall: use mcp__vedix__search_knowledge_index for similar hypotheses.

  2. Generate hypothesis.md with these sections:

## Hypothesis
<Clear, testable hypothesis statement>

## Mathematical Models
<Key equations in proper LaTeX environments>
Use \begin{equation}...\end{equation} for numbered equations.
Use \begin{align}...\end{align} for multi-line derivations.
Use inline $...$ for symbols in text.
Every equation must have a brief verbal explanation.

## Statistical Framework
<For domains requiring statistical rigor>
- Null and alternative hypotheses (H0, H1)
- Test selection rationale (parametric vs non-parametric)
- Significance level (alpha)
- Multiple comparison correction method
- Effect size measure
- Confidence interval method
- Power analysis if sample sizes are fixed

## Methodology
- Libraries: <from template>
- Experiment type: <from template>
- Evaluation metric: <from template>
- Data sources: <synthetic or real?>
- Output artifacts: results.csv, .npy, plot_results.png
- **Dependency list**: ALL pip packages needed (for requirements.txt)

## Codebase Integration (if applicable)
- New modules to create
- Existing modules to extend
- API contracts to maintain

## Literature Grounding
<Which papers support each claim — cite by BibTeX key>
  1. Avoid prior failures: if domain has high failure rate from prior_failures, simplify methodology.

Read the full file on GitHub · 96 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 · 96 lines · 36 tokens per session scan A 6d25554a98b9

Subscribe to this mod's changes

vedix-hypothesizer is an agent published in the GitHub repository danilkotelnikov/vedix (3 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 775 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.

Related

Other agents, from other repositories

wtfp-outliner

Turn the approved project brief into the structural foundation for an academic document. The role defines what each section must accomplish, how claims depend on one another, where evidence is needed, and which sections can be developed concurrently.

akougkas/wtf-p · 48 tokens

wtfp-section-writer

Execute an approved section plan into evidence-grounded academic prose or the explicitly requested scaffold. Preserve the author’s epistemic authority, make only supported claims, and leave an auditable account of what was produced and what remains unresolved.

akougkas/wtf-p · 51 tokens

wtfp-section-reviewer

Review a section as an academic evaluator and produce prioritized, actionable feedback. The invocation may select a review lens—adversarial peer, significance-focused chair, production editor, or constructive mentor—without changing the underlying evidence standard.

akougkas/wtf-p · 51 tokens

editor

Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].

pedrohcgs/claude-code-my-workflow · 64 tokens

mathodology-problem-analyst

Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.

sweetcornna/mathodology · 29 tokens

prompt_engineer

Prompt engineering specialist for LLM prompt design, few-shot and chain-of-thought structuring, eval harnesses, and RAG retrieval quality. Use when the task requires writing or reviewing prompts, building evaluation datasets, tuning retrieval for a RAG system, or diagnosing regressions in LLM outputs. For example…

josstei/maestro-orchestrate · 98 tokens