list-assumptions

list-assumptions is a command for Claude Code from akougkas/wtf-p. It costs 14 tokens per session (635 once invoked), scanned A, a copy of add-todo, MIT.

A read-only command that lists the assumptions behind a paper section and labels their status, such as supported, disputed, or unverified.

In plain words
What is it for?
Use it to inspect the assumptions behind a section's claims, outline, decisions, and evidence.
Why use it?
It exposes hidden decisions before writing changes are made, without altering project files.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the wtfp plugin — 36 commands, 3 hooks shipped together

Good fit Use it to inspect the assumptions behind a section's claims, outline, decisions, and evidence.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add akougkas/wtf-p
Claude Code
/plugin install wtfp

Made for: Claude Code.

Or install wtfp, the plugin that ships this one along with the rest of its 36 commands, 3 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/akougkas/wtf-p/list-assumptions/github.svg)](https://agentmods.dev/commands/akougkas/wtf-p/list-assumptions)
Your own site
<a href="https://agentmods.dev/commands/akougkas/wtf-p/list-assumptions"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/list-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 list-assumptions

Your own site · 80×15
<a href="https://agentmods.dev/commands/akougkas/wtf-p/list-assumptions"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/list-assumptions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 635 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 81% copy Near-identical to another mod 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.00014 $0.00635
Opus 5.5 $0.00006 $0.00254
Sonnet 5.5 $0.00003 $0.00127
Haiku 4.5 $0.00001 $0.00064

Measured 29d ago against content hash e8d3787c0ad4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

list-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 29d 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.

Origin

This is a copy

81% identical to add-todo — 34 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

vendors/claude/commands/list-assumptions.md · 59 lines

How it starts

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

List section assumptions

@${CLAUDE_PLUGIN_ROOT}/project/README.md @${CLAUDE_PLUGIN_ROOT}/skills/wtfp-plan-section/SKILL.md @${CLAUDE_PLUGIN_ROOT}/skills/wtfp-plan-section/references/actions.md

Record contract

Read: project://manifest, project://decisions, project://structure/outline, project://sections/{section}. Produce: none.

Resolve every logical URI through the host adapter. Portable v1 JSON records are the source of truth: schema-validate before a write, preserve stable IDs, update revision and timestamps where required, and replace records atomically. Never pass a literal logical URI to a shell command or infer record state from a legacy Markdown control file.

Manuscript prose and supporting context, research, plan, review, summary, handoff, and deliverable artifacts retain their authored format (normally Markdown). Link them from the relevant v1 record; do not convert manuscript prose into project-state JSON.

Procedure

  1. Extract explicit and implicit assumptions from manifest, decisions, outline, section claims, and evidence.
  2. Classify each as locked, deferred, discretionary, supported, disputed, or unverified and cite its source URI.
  3. Return findings only; recommend a separate author decision or research action for unresolved assumptions.

Safety and completion

Do not initialize a repository or run branch, stage, commit, merge, push, or publish operations. If requested, return a clearly labeled optional handoff for a separately authorized action.

Report the logical resources read, created, updated, archived, or deleted; the gates crossed; validation results; unresolved checkpoints; and the safest next action. Never claim a mutation that was not verified.

Bound action contract and schemas

@${CLAUDE_PLUGIN_ROOT}/actions/list-assumptions.json @${CLAUDE_PLUGIN_ROOT}/project/schemas/common.schema.json @${CLAUDE_PLUGIN_ROOT}/project/schemas/decisions.schema.json @${CLAUDE_PLUGIN_ROOT}/project/templates/decisions.json @${CLAUDE_PLUGIN_ROOT}/project/schemas/manifest.schema.json @${CLAUDE_PLUGIN_ROOT}/project/templates/manifest.json @${CLAUDE_PLUGIN_ROOT}/project/schemas/outline.schema.json @${CLAUDE_PLUGIN_ROOT}/project/templates/outline.json @${CLAUDE_PLUGIN_ROOT}/project/schemas/section.schema.json @${CLAUDE_PLUGIN_ROOT}/project/templates/section.json

Read the full file on GitHub · 59 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. 29d ago Changed e8d3787c0ad4
  2. 1mo ago First seen · 59 lines · 14 tokens per session scan A 6e8d96b0f9b3

Subscribe to this mod's changes

list-assumptions is a command published in the GitHub repository akougkas/wtf-p (20 stars, last pushed 11d ago), licensed MIT. It adds 14 tokens to every session and 635 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 81% identical to add-todo, differing in 34 lines, and is treated as a copy.