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 Emasoft/ai-maestro-architect-agent --skill amaa-hypothesis-verification-opsgit clone --depth 1 https://github.com/Emasoft/ai-maestro-architect-agentWrote 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/emasoft/ai-maestro-architect-agent/amaa-hypothesis-verification-ops)<a href="https://agentmods.dev/skills/emasoft/ai-maestro-architect-agent/amaa-hypothesis-verification-ops"><img src="https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-hypothesis-verification-ops/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/emasoft/ai-maestro-architect-agent/amaa-hypothesis-verification-ops"><img src="https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-hypothesis-verification-ops.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.00036 | $0.00482 |
| Opus 5 | $0.00018 | $0.00241 |
| Sonnet 5 | $0.00007 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
amaa-hypothesis-verification-ops 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hypothesis Verification Operations
Overview
Operational references for hypothesis verification: the multiplicity rule for testing 3+ approaches, report templates, and quick-reference classifications.
Prerequisites
- Familiarity with the core hypothesis verification workflow
Instructions
- Apply the Multiplicity Rule: generate 3+ candidate approaches
- Use output templates to document experiment results
- Classify findings using status codes from quick reference
- Archive prototypes only when code is essential to explain findings
Checklist
Copy this checklist and track your progress:
- Generate 3+ candidate approaches per hypothesis
- Document each experiment using the report template
- Classify results (VERIFIED/UNVERIFIED/PARTIALLY VERIFIED)
- Archive or delete experimental code per policy
Reference Documents
| Document | Content |
|---|---|
| multiplicity-rule.md | The Multiplicity Process, Example: Implementing a Paper Algorithm, Iterative Selection Workflow |
| output-templates.md | Experiment Directory Structure, Experimentation Report Template, Hypothesis, Candidates Tested, Experimental Setup, Results, Evidence-Based Conclusions |
| quick-reference.md | Status Classifications, Implementation vs Experimental Code, Workflow Integration Points, IRON RULES Summary, Examples |
Examples
Example: Test 3+ Redis configurations in Docker, measure latency, select winner by evidence, document in REPORT.md
Error Handling
| Issue | Fix |
|---|---|
| Too few candidates | Add approaches until 3+ exist |
| Inconclusive results | Increase sample size or iterations |
Output
| Type | Description |
|---|---|
| Experimentation Report | experiments/<claim>/REPORT.md with template |
| Prototype Archive | docs_dev/experiments/<claim>/prototypes/ if needed |
Resources
See Reference Documents table above.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 65 lines · 36 tokens per session scan A 563e8713f3ca
amaa-hypothesis-verification-ops is a skill published in the GitHub repository Emasoft/ai-maestro-architect-agent (2 stars, last pushed 12d ago), licensed MIT. It adds 36 tokens to every session and 482 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.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…