agentmods.dev

hypothesis-tree

hypothesis-tree is a skill for Claude Code from daddia/claude-for-strategy. It costs 58 tokens per session (732 once invoked), scanned A, original, MIT.

A diagram-like breakdown of a problem into smaller claims that can be tested with evidence. The branches are designed to cover different explanations without unnecessary overlap.

In plain words
What is it for?
Use it to restate a problem as a question, propose a testable main explanation, split it into three to five sub-hypotheses, and define the evidence needed for each branch. It structures the investigation but does not perform it.
Why use it?
It turns a broad or unclear question into a focused set of checks before analysis begins. This makes it easier to see what evidence is missing and which assumptions matter.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Part of the consulting plugin — 9 skills shipped together

not rated 2repo 4mo ago A scan 58 tokens original MIT

Good fit Use it to restate a problem as a question, propose a testable main explanation, split it into three to five sub-hypotheses, and define the evidence needed for each branch. It structures the investigation but does not perform it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/daddia/claude-for-strategy/hypothesis-tree
View source ↗ daddia/claude-for-strategy
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.

Any agent
npx skills add daddia/claude-for-strategy --skill hypothesis-tree
Clone the repo
git clone --depth 1 https://github.com/daddia/claude-for-strategy

Made for: Claude Code.

Or install consulting, the plugin that ships this one along with the rest of its 9 skills.

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-tree

README.md
[![agentmods](https://agentmods.dev/badge/skills/daddia/claude-for-strategy/hypothesis-tree/github.svg)](https://agentmods.dev/skills/daddia/claude-for-strategy/hypothesis-tree)
Your own site
<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/hypothesis-tree"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/hypothesis-tree/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.

agentmods 80×15 button for hypothesis-tree

Your own site · 80×15
<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/hypothesis-tree"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/hypothesis-tree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 732 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00058 $0.00732
Opus 5.5 $0.00023 $0.00293
Sonnet 5.5 $0.00012 $0.00146
Haiku 4.5 $0.00006 $0.00073

Measured 2mo ago against content hash 3e1229fee5a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

hypothesis-tree 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 2mo 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.

consulting/skills/hypothesis-tree/SKILL.md · 90 lines

How it starts

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

Hypothesis Tree

When to use

Break a problem into falsifiable root and MECE sub-hypotheses before analysis. See ../../references/hypothesis-driven-approach.md.

What this skill does not do

  • Does not run analysis — names evidence needed; workplan-builder executes.
  • Does not use topic labels as nodes — every node falsifiable.
  • Does not keep branches with no so-what either direction — cut and list.

Preconditions

Input If missing
Problem as question Restate and confirm before tree
Root hypothesis ambiguity Present both roots; ask which to build

Provisional mode

Uncertain root: two candidate roots with user choice; label structured first pass.

Trust spine

  • Analytical Rigor (mandatory): MECE sub-hypotheses; evidence-needed per branch; cut branches listed.
  • Confidence bands (hypothesis-driven-analysis): High = triangulated evidence plan; Medium = single source; Low = assumption-driven — label load-bearing assumption.
  • Per trust-conventions.md for sourcing, numbers, gate.

Workflow

  1. Restate problem as question; confirm.
  2. Propose falsifiable root hypothesis.
  3. 3–5 MECE sub-hypotheses.
  4. Smallest evidence test per sub-hypothesis.
  5. So-what if TRUE and if FALSE; cut if neither matters.
  6. Output as tree.

Output format

ROOT HYPOTHESIS: [falsifiable claim]

1. [Sub-hypothesis 1]
   Evidence needed: [...]
   If TRUE: [...]
   If FALSE: [...]
...

Cut branches: [...]

Worked example

Input: "Why did mid-tier churn spike?"

Excerpt: Root: price increase caused mid-tier churn. Sub-hypothesis: elasticity >15% in segment; evidence: cohort comparison Q1 vs Q4.

Quality checks before delivering

  • Falsifiable nodes only
  • MECE check explicit
  • Cut branches documented
  • Handoff-ready for workplan-builder

Propose profile update

When a stable convention surfaces during this run (thresholds, naming, tone, output format, or recurring corrections), propose a profile update: show the exact diff against ~/.claude/plugins/config/claude-for-strategy/consulting/CLAUDE.md (org-wide facts go to org-profile.md), ask for confirmation, and write only on yes. Only /consulting:practice-setup auto-applies a full profile write.

Read the full file on GitHub · 90 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. 2mo ago First seen · 90 lines · 58 tokens per session scan A 3e1229fee5a2

Subscribe to this mod's changes

hypothesis-tree is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 732 once invoked, about $0.0002 per session on Opus 5.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.

ConnectorsPlanningagentsclaudecursormcpskills
Related

Other skills, from other repositories

review

Run the full pre-merge panel: parallel audit and lens reviewers over a diff, consolidated into one severity-ranked verdict.

helderberto/agent-skills · 0 tokens

tdd

Test-driven development, from unit to end-to-end tests. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration or end-to-end tests (Playwright, Cypress). Don't use to backfill tests on existing code (/refactor) or diagnose an unknown bug (/debug).

helderberto/agent-skills · 71 tokens

visual-review

Two visual modes — render a PR diff as an HTML page with each hunk annotated by principle, or check a UI change in a real browser (screenshots, console, network). Use for a visual/HTML diff report, "check the UI", or "screenshot before/after". Don't use for text-only feedback (/code-review), unit tests (/tdd), or full…

helderberto/agent-skills · 84 tokens

to-pr

Gate, push, and open a GitHub pull request on the repo's PR template, then watch CI.

helderberto/agent-skills · 25 tokens

to-tickets

Slice a spec or a ticket into tracer-bullet tickets with blocking edges, published through the repo's tracker: .specs/tickets/ .md by default.

helderberto/agent-skills · 0 tokens

debate

Settle a go/no-go on one risky change against an alternative through an advocate, a skeptic, and a neutral investigator.

helderberto/agent-skills · 28 tokens