map-assumptions

map-assumptions is a skill for Claude Code from tomzx/agents. It costs 35 tokens per session (491 once invoked), scanned A, original, MIT.

A product-validation process that lists the beliefs and risks an opportunity depends on, then ranks them by impact and uncertainty. It covers whether customers want the idea, whether the business can sustain it, whether it can be built, and whether people can use it.

In plain words
What is it for?
Use it to document assumptions, confidence levels, supporting evidence, and the one to three highest-priority assumptions to test first.
Why use it?
It makes hidden risks visible and focuses testing on the few assumptions whose failure could invalidate the whole opportunity.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it to document assumptions, confidence levels, supporting evidence, and the one to three highest-priority assumptions to test first.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tomzx/agents/map-assumptions
View source ↗ tomzx/agents
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 tomzx/agents --skill map-assumptions
Clone the repo
git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code.

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 map-assumptions

README.md
[![agentmods](https://agentmods.dev/badge/skills/tomzx/agents/map-assumptions/github.svg)](https://agentmods.dev/skills/tomzx/agents/map-assumptions)
Your own site
<a href="https://agentmods.dev/skills/tomzx/agents/map-assumptions"><img src="https://agentmods.dev/badge/skills/tomzx/agents/map-assumptions/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 map-assumptions

Your own site · 80×15
<a href="https://agentmods.dev/skills/tomzx/agents/map-assumptions"><img src="https://agentmods.dev/badge/skills/tomzx/agents/map-assumptions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 491 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.00035 $0.00491
Opus 5 $0.00017 $0.00246
Sonnet 5 $0.00007 $0.00098
Haiku 4.5 $0.00003 $0.00049

Measured 5d ago against content hash 0dd074f73a0f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

map-assumptions 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 5d 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.

skills/pdlc/skills/map-assumptions/SKILL.md · 45 lines

What it actually says

Map Assumptions

Validate begins by making the invisible explicit. For the opportunity that survived the Discover gate, enumerate everything that must be true for it to work, then rank by leverage (impact x uncertainty) so the next skill tests the few assumptions whose falsity would kill the whole thing.

Prerequisites

  • Apply the shared PDLC conventions in skills/pdlc/references/shared.md.
  • opportunity-tree.md with a proceed gate from Discover.

Steps

  1. Read the chosen opportunity and its candidate solutions from opportunity-tree.md.
  2. Surface assumptions across four categories:
    • Desirability — do they want this? (problem real, willingness to adopt/pay)
    • Viability — does it work for the business? (pricing, unit economics, channel)
    • Feasibility — can we build/operate it? (tech, data, ops, partners)
    • Usability — can they actually use it? (workflow fit, effort)
  3. For each assumption, record: the belief, why it matters, current confidence (low/med/high), and the evidence that would change your mind.
  4. Rank by leverage = impact (if false, how bad) x uncertainty (how unsure). The top 1-3 are the leap-of-faith assumptions — the ones Validate must test.
  5. Write assumptions.md to the initiative directory.

Output Format

Use the template at skills/pdlc/templates/initiatives/assumptions.md. Carry the standard initiative frontmatter with phase: validate.

Outcome

If $OUTCOME_YAML is set, emit verdict: drafted.

Completion Checklist

  • Assumptions cover all four categories (desirability, viability, feasibility, usability)
  • Each assumption has a confidence level and a falsifying signal
  • The top 1-3 leap-of-faith assumptions are explicitly marked

Next Step

Load design-experiment to design the cheapest decisive test for the top leap-of-faith assumptions.

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. 5d ago First seen · 45 lines · 35 tokens per session scan A 0dd074f73a0f

Subscribe to this mod's changes

map-assumptions is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 491 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-09-03.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens