assumptions

assumptions is a skill for Claude Code from Kastalien-Research/thoughtbox. It costs 32 tokens per session (919 once invoked), scanned A, original, MIT.

A registry for recording beliefs about dependencies, tools, the environment, or how a system behaves, along with evidence and verification details.

In plain words
What is it for?
Use it to list assumptions, add new records, verify whether a claim is still true, and track the impact when one is wrong.
Why use it?
It prevents the team from repeatedly rediscovering known failures and makes uncertain information easier to review.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to list assumptions, add new records, verify whether a claim is still true, and track the impact when one is wrong.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kastalien-research/thoughtbox/assumptions
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 Kastalien-Research/thoughtbox --skill assumptions
Clone the repo
git clone --depth 1 https://github.com/Kastalien-Research/thoughtbox

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 assumptions

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/kastalien-research/thoughtbox/assumptions"><img src="https://agentmods.dev/badge/skills/kastalien-research/thoughtbox/assumptions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 919 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00032 $0.00919
Opus 5.5 $0.00013 $0.00368
Sonnet 5.5 $0.00006 $0.00184
Haiku 4.5 $0.00003 $0.00092

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

Security

Grade A, and why

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 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.

.agents/skills/assumptions/SKILL.md · 98 lines

How it starts

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

Manage assumptions: $ARGUMENTS

Commands

Parse the first word of $ARGUMENTS to determine the command:

list — Show all tracked assumptions

  1. Read all .assumptions/*.jsonl files
  2. Parse each line as a JSON record
  3. Display sorted by confidence (lowest first) or staleness (oldest verification first)
  4. Format as a table: ID | Category | Claim | Confidence | Last Verified | Status

add — Register a new assumption

Parse remaining arguments for: --category, --claim, --evidence, --source

Create a new assumption record in .assumptions/registry.jsonl:

{
  "id": "<category>-<short-slug>",
  "category": "<api|dependency|behavior|environment|tooling>",
  "claim": "<what we assume to be true>",
  "evidence": "<what supports this assumption>",
  "source": "<where this was discovered>",
  "confidence": 0.8,
  "created": "<ISO 8601>",
  "last_verified": "<ISO 8601>",
  "verification_method": "<how to test this>",
  "failure_history": [],
  "status": "active",
  "blast_radius": "<what breaks if this assumption is wrong>"
}

verify — Re-verify an assumption

  1. Read the assumption record by ID
  2. Execute the verification method (may involve web search, API calls, or code checks)
  3. Update last_verified timestamp and confidence score
  4. If verification fails, add to failure_history and reduce confidence
  5. If confidence drops below 0.3, mark status as suspect and warn

stale — Show assumptions that need re-verification

  1. Read all assumption records
  2. Filter to those where last_verified is more than 14 days ago
  3. Sort by blast_radius (highest first)
  4. Display with suggested verification actions

seed — Seed registry from MEMORY.md gotchas

  1. Read MEMORY.md
  2. Extract entries from "Gotchas", "Known Bugs", and "MCP Knowledge API Gotchas" sections
  3. For each entry, create an assumption record with:
    • category: inferred from content (api, dependency, behavior, etc.)
    • claim: the gotcha statement
    • evidence: "Discovered empirically" + date from MEMORY.md
    • confidence: 0.9 (verified by experience)
    • verification_method: suggested test

Read the full file on GitHub · 98 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. 1mo ago First seen · 98 lines · 32 tokens per session scan A dd7607981f4e

Subscribe to this mod's changes

assumptions is a skill published in the GitHub repository Kastalien-Research/thoughtbox (65 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 919 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.

Related

Other skills, from other repositories

handoff

Resume the most recent agent session for the current working directory, leading with any unanswered question. Use when the user says "where were we", "resume", "handoff", "pick up where I left off", or starts a session with no fresh context.

rohitg00/agentmemory · 55 tokens

agentmemory-agents

How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.

rohitg00/agentmemory · 46 tokens

agentmemory-hooks

The agentmemory plugin hooks that capture observations automatically across the agent session lifecycle. Use when explaining how memory gets captured without manual saves, when debugging missing observations, or when tuning what gets recorded.

rohitg00/agentmemory · 42 tokens

run-memory

Shared step of the marketing playbooks (analyze-performance, run-paid-campaigns, research-competitors, email-lifecycle): reads the last run's record, checks whether its recommendations were done and whether they worked, and saves a short record of this run for the next one. Loaded by those playbooks; not for direct…

gooseworks-ai/goose-skills · 72 tokens

save-learning

Shared step of the marketing playbooks (make-static-ads, analyze-performance, email-lifecycle, write-outreach): saves a short brand rule or finding in the human's own words, one idea per rule, retires the playbook's own older rules it replaces, and reads the result back to confirm. Loaded by those playbooks; not for…

gooseworks-ai/goose-skills · 77 tokens

lc-curate-context

Decide which files a task actually needs, record that as a reusable llm-context rule, verify it against the codebase - including the files your selection references but leaves out - and pack it for your own context, a chat, or a sub-agent you dispatch. Load when choosing what code to put in front of a model, packing…

cyberchitta/llm-context.py · 90 tokens