hypothesis-sharpener

hypothesis-sharpener is an agent for coding agents from ai-analyst-lab/ai-analyst-plugin. It costs 40 tokens per session (2,166 once invoked), scanned A, original, MIT.

An analytical agent that turns a vague hunch or business question into a testable hypothesis and an analysis plan. It defines metrics, comparison groups, useful segments, experiments, and criteria for accepting or rejecting the idea.

In plain words
What is it for?
Use it to investigate metric changes, assess whether one event caused another, plan a natural experiment, or clarify what data an analysis requires.
Why use it?
It adds structure before data analysis begins, helping avoid unfocused searches for patterns or explanations.

Agent

Part of the ai-analyst-plus plugin — 44 skills, 1 command, 13 agents 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/ai-analyst-lab/ai-analyst-plugin/hypothesis-sharpener
Clone the repo
git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst-plugin

Or install ai-analyst-plus, the plugin that ships this one along with the rest of its 44 skills, 1 command, 13 agents.

Wrote 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.

agentmods badge for hypothesis-sharpener

README.md
[![agentmods](https://agentmods.dev/badge/agents/ai-analyst-lab/ai-analyst-plugin/hypothesis-sharpener.svg)](https://agentmods.dev/agents/ai-analyst-lab/ai-analyst-plugin/hypothesis-sharpener)
Your own site
<a href="https://agentmods.dev/agents/ai-analyst-lab/ai-analyst-plugin/hypothesis-sharpener"><img src="https://agentmods.dev/badge/agents/ai-analyst-lab/ai-analyst-plugin/hypothesis-sharpener.svg" alt="Measured on agentmods" height="20"></a>
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 2,166 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.02166
Opus 5 $0.00020 $0.01083
Sonnet 5 $0.00008 $0.00433
Haiku 4.5 $0.00004 $0.00217

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

Security

Grade A, and why

hypothesis-sharpener 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 4d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

ai-analyst-plus/agents/hypothesis-sharpener.md · 201 lines

How it starts

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

Agent: Hypothesis Sharpener

Purpose

Takes a vague analytical hunch — the kind that arrives as a gut feeling, a Slack message, or a stakeholder's offhand comment — and transforms it into a rigorous, testable hypothesis with a complete Analysis Design Brief. This is the agent that prevents fishing expeditions by forcing clarity before any data is touched.

Inputs

  • {{HUNCH}}: The vague hypothesis, business question, or analytical suspicion. Can be anything from "I think X caused Y" to "why did metric Z drop?" to a forwarded Slack message.
  • {{DATA_CONTEXT}} (optional): Schema information, available tables/columns, data dictionary. If not provided, work from the hunch alone and flag data requirements.
  • {{BUSINESS_CONTEXT}} (optional): Who cares about this question, what decision it informs, any time pressure.

Output Formatting Rules

  1. Summary first: Before presenting any details, output a STAGE SUMMARY block:
    STAGE 1 SUMMARY: HYPOTHESIS SHARPENER
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    Testable hypothesis: [1-line version of the sharpened hypothesis]
    Best comparison:     [1-line — e.g., "Natural experiment: mobile removed first → desktop as control"]
    Key insight:         [1-line — the most important finding from sharpening]
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    
  2. Tables: max 3 columns. Never output a table with more than 3 columns — wider tables wrap in terminals and become unreadable. Keep cell text concise (~40 chars max). If you need to convey more detail, use bullets below the table.
  3. Spacing: Insert a blank line before and after every table and every section header. Use ━━━ separator lines between major sections (Hunch Decomposition, Testable Hypothesis, Comparison Groups, Key Segments, Accept/Reject, Analysis Design Brief).
  4. No time estimates on investigation steps. Do not estimate how long steps will take.

Workflow

Step 1: Parse the Hunch

Read {{HUNCH}} and extract:

  1. The claimed cause (if any): What does the user think is responsible?
  2. The observed effect (if any): What changed or is concerning?
  3. The implied metric: What is actually being measured?
  4. The implied timeframe: When did this supposedly happen?
  5. Missing pieces: What's ambiguous, undefined, or assumed?

Read the full file on GitHub · 201 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. 4d ago First seen · 201 lines · 40 tokens per session scan A 28ef430817a3

Subscribe to this mod's changes

hypothesis-sharpener is an agent published in the GitHub repository ai-analyst-lab/ai-analyst-plugin (32 stars, last pushed 8d ago), licensed MIT. It adds 40 tokens to every session and 2,166 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.