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 itseffi/agentic-os --skill assumption-mappinggit clone --depth 1 https://github.com/itseffi/agentic-osWrote 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/itseffi/agentic-os/assumption-mapping)<a href="https://agentmods.dev/skills/itseffi/agentic-os/assumption-mapping"><img src="https://agentmods.dev/badge/skills/itseffi/agentic-os/assumption-mapping/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/itseffi/agentic-os/assumption-mapping"><img src="https://agentmods.dev/badge/skills/itseffi/agentic-os/assumption-mapping.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.00024 | $0.00410 |
| Opus 5.5 | $0.00010 | $0.00164 |
| Sonnet 5.5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
assumption-mapping 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 1mo 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.
What it actually says
Assumption Mapping
Generate and categorize assumptions underlying a product strategy.
When to Use
Early in product development to surface and document what you're betting on.
The Framework
Organize assumptions into four categories:
| Category | Focus | Example Questions |
|---|---|---|
| Desirability | Will users want this? | Problem severity, willingness to pay, switching triggers |
| Feasibility | Can we build it? | Technical risks, data needs, integrations, security |
| Viability | Will it make money? | Pricing, margins, retention, unit economics |
| Usability | Can users use it? | Task success, learnability, error tolerance |
The Process
1. Gather Inputs
Document:
- Product description
- Core problem being solved
- Target user
2. Generate Assumptions
For each category, create at least 5 assumptions:
Format:
- Statement: "We believe that [specific, falsifiable claim]"
- Impact if wrong: [concrete consequence]
Good example:
- Statement: "We believe that SMB admins will pay $20/user/month if onboarding drops below 30 minutes"
- Impact if wrong: Premium pricing underperforms due to insufficient WTP
3. Quality Check
Each assumption should be:
- Specific (include numbers, segments, timeframes)
- Testable (you could run an experiment)
- One idea per assumption (no compound claims)
Output
Four lists of 5+ assumptions each:
- Desirability assumptions
- Feasibility assumptions
- Viability assumptions
- Usability assumptions
Each with statement and impact if wrong.
When Not to Use
Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.
What ships with it
1 file 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.
- 1mo ago First seen · 66 lines · 24 tokens per session scan A 229452939502
assumption-mapping is a skill published in the GitHub repository itseffi/agentic-os (117 stars, last pushed 14d ago), licensed MIT. It adds 24 tokens to every session and 410 once invoked, about $0.0001 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-30.
Other skills, from other repositories
vague-requirement-unpacker
A planning aid for turning a vague business request into questions, a narrowed scenario, and an initial scope outline. It is meant for early alignment before a full PRD, or product requirements document, exists.
reviewcourt
A review tool for completed Tencent Meeting requirements or technical-plan meetings. It turns the meeting notes and transcript into a verdict, such as approved, conditionally approved, rejected, or lacking enough information.
competitive-product-research
A research workflow for comparing products and explaining how they differ. It examines user experience and business strategy, then produces a report in HTML or Markdown with traceable sources.
opc-board
A review skill for testing whether a one-person business, side project, or open-source idea is practical. Five advisers score its logic, ability to be delivered, growth potential, viability, and risks, then give a Go or No-Go result.
pm-requirement-review-simulator
A rehearsal for reviewing a product requirements document, or PRD—a written description of what a product or feature should do. Five cross-functional roles challenge the requirements before the real meeting.
ide-briefing-ppt
Generates a single-file 1280x720 HTML presentation by reusing the frozen Light IDE visual system extracted from LLM Wiki 分享.html. Use only when the user names ide-briefing-ppt, asks to reuse that deck's UI, or explicitly requests the combined light-gray canvas, white panels, amber accent, terminal, and file-tree…