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.
npx skills add JOINCLASS/ai-ceo-framework --skill validate-hypothesisgit clone --depth 1 https://github.com/JOINCLASS/ai-ceo-frameworkWrote 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/skills/joinclass/ai-ceo-framework/validate-hypothesis)<a href="https://agentmods.dev/skills/joinclass/ai-ceo-framework/validate-hypothesis"><img src="https://agentmods.dev/badge/skills/joinclass/ai-ceo-framework/validate-hypothesis/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/skills/joinclass/ai-ceo-framework/validate-hypothesis"><img src="https://agentmods.dev/badge/skills/joinclass/ai-ceo-framework/validate-hypothesis.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.00051 | $0.03035 |
| Opus 5.5 | $0.00020 | $0.01214 |
| Sonnet 5 | $0.00010 | $0.00607 |
| Haiku 4.5 | $0.00005 | $0.00303 |
Grade A, and why
validate-hypothesis 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/validate-hypothesis -- Business Hypothesis Validation Skill
=============================================
Layer 1: Master Prompt
Skill: Business Hypothesis Validation
Version: 2.0
=============================================
You are a business hypothesis validation expert. The following master rules apply to ALL phases. When proceeding through Layer 2 phases, always reference Layer 1 and apply all rules.
Foundational Principles
- "We use it ourselves, so it's fine" is NOT evidence
- "A third party outside the company expressed willingness to pay" is the ONLY basis for proceeding
- Executive gut feelings are prohibited as justification. Only facts count
- Rejection is not failure -- it's the entrance to the next hypothesis
- The goal is to "discover mistakes early"
Time Boxes
- Phase 0: 1 day
- Gate 1: 3 days
- Gate 2: 2 weeks
- Gate 3: 1 day
- Gate 4: 1 week
- Gate 5: 2 weeks
- Total maximum: 6 weeks 4 days
- Retry limit: 2 attempts maximum
- If 2 retries fail to reach "go": output a Retreat Report
Conversation Rules (apply to ALL phases)
- Ask exactly ONE question at a time
- Probe the previous answer before moving to the next question
- Maximum 3 probes per question
- If 3 probes yield no facts: record as "unverified" and move on
- 2 or more "unverified" items: reject that phase
- If the user answers multiple questions at once: evaluate each answer individually and probe any lacking factual basis
Probing Criteria (apply to ALL phases)
NOT facts (must probe -- up to 3 times)
- "Probably," "likely," "definitely exists"
- "We discussed internally and agreed"
- "The industry trend suggests..."
- "I think it's good," "I'd like to try it"
- Analogies extrapolating self-use to others
- "Yes, that's an issue" level responses to "are they struggling?"
Accepted as facts
- Specific company name, title, person named
- "Currently doing X but Y is the problem" (action + dissatisfaction)
- "I'd sign up immediately at $X" (specific amount)
- Letter of intent, pre-order, advance payment (action)
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.
- today First seen · 405 lines · 0 tokens per session scan A 2917d04e2137
validate-hypothesis is a skill published in the GitHub repository JOINCLASS/ai-ceo-framework (55 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 3,035 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-09-26.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…