think-belief-update-routine

think-belief-update-routine is a skill for Claude Code, Codex from product-on-purpose/thinking-framework-skills. It costs 126 tokens per session (1,806 once invoked), scanned A, original, Apache-2.0.

A recurring record for reviewing how confident you are in open beliefs, forecasts, or assumptions as new evidence arrives.

In plain words
What is it for?
Use it to track strategic assumptions, forecasts, or other important beliefs over time and decide when each should be reviewed again.
Why use it?
It makes belief changes explicit instead of letting outdated assumptions quietly persist. Each review records the previous confidence, new evidence, revised confidence, and reason for the change.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Part of the thinking-framework-skills plugin — 68 skills, 10 commands, 1 agent shipped together

Good fit Use it to track strategic assumptions, forecasts, or other important beliefs over time and decide when each should be reviewed again.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/product-on-purpose/thinking-framework-skills/think-belief-update-routine
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 product-on-purpose/thinking-framework-skills --skill think-belief-update-routine
Clone the repo
git clone --depth 1 https://github.com/product-on-purpose/thinking-framework-skills

Made for: Claude Code, Codex.

Or install thinking-framework-skills, the plugin that ships this one along with the rest of its 68 skills, 10 commands, 1 agent.

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 think-belief-update-routine

README.md
[![agentmods](https://agentmods.dev/badge/skills/product-on-purpose/thinking-framework-skills/think-belief-update-routine/github.svg)](https://agentmods.dev/skills/product-on-purpose/thinking-framework-skills/think-belief-update-routine)
Your own site
<a href="https://agentmods.dev/skills/product-on-purpose/thinking-framework-skills/think-belief-update-routine"><img src="https://agentmods.dev/badge/skills/product-on-purpose/thinking-framework-skills/think-belief-update-routine/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 think-belief-update-routine

Your own site · 80×15
<a href="https://agentmods.dev/skills/product-on-purpose/thinking-framework-skills/think-belief-update-routine"><img src="https://agentmods.dev/badge/skills/product-on-purpose/thinking-framework-skills/think-belief-update-routine.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 126 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,806 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.00126 $0.01806
Opus 5 $0.00063 $0.00903
Sonnet 5 $0.00025 $0.00361
Haiku 4.5 $0.00013 $0.00181

Measured 12d ago against content hash 43387a896ca6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

think-belief-update-routine 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 12d 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/think-belief-update-routine/SKILL.md · 68 lines

How it starts

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

Belief-Update Routine

A belief-update routine re-scores a standing inventory of open beliefs against newly arrived evidence, on a cadence. For each tracked belief it records a prior confidence, the evidence accrued since the last review, a revised confidence with an explicit delta and direction, a stated reason for the size of the move, and a next-review trigger. The load-bearing move is the disciplined, recurring re-score of a portfolio over time: it makes under-updating (the robust human tendency to revise too little for the evidence) visible and correctable, and it keeps beliefs that should track reality - open forecasts, strategic theses, standing assumptions - honest against new information rather than quietly stale. The output is a structured belief-update ledger, not prose, designed to be reopened and re-scored on the next cadence.

When to Use

  • When you hold a set of consequential, genuinely open beliefs, forecasts, or standing assumptions that should track reality over time, and you want a recurring, disciplined re-score rather than a one-off.
  • When genuinely new evidence has arrived since you last examined them, so there is something real to update on.
  • When you suspect you are under-updating - holding a belief sticky as evidence accumulates against it - and you want the size of each update made explicit and checkable.
  • When you want to build calibration on standing beliefs over many cycles, not judge a single decision.

When NOT to Use

  • To record a single decision at the moment it is made. That is think-decision-journal, which fixes one prediction in place at commit time and forbids editing it afterward. This routine is the opposite shape: it deliberately re-scores a portfolio of open beliefs repeatedly. Do not use it to capture a one-off decision (you lose the journal's contemporaneous lock), and do not use the journal to track evolving beliefs (you violate its do-not-edit rule).
  • To review a finished episode against what was expected. That is think-after-action-review, which needs a resolved outcome and emits sustain/change process actions. This routine operates on beliefs that are still open and emits revised confidences, not action items.
  • To surface the conditions under which one contested claim would be the best choice. That is think-what-would-have-to-be-true, which decomposes a single claim into its load-bearing conditions at one sitting. This routine re-scores a portfolio of beliefs on a cadence against accrued evidence.
  • When no genuinely new evidence has arrived. Re-scoring on a calendar with nothing new is reflection theater: it manufactures motion or just re-anchors the prior. If nothing material has changed, the honest entry is "no new evidence; no update," not an invented delta.
  • For beliefs that never resolve and carry no real stakes. Re-scoring trivia delivers no calibration and no decision value; the overhead is unrecovered.

Read the full file on GitHub · 68 lines

Files

What ships with it

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

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. 12d ago First seen · 68 lines · 126 tokens per session scan A 43387a896ca6

Subscribe to this mod's changes

think-belief-update-routine is a skill published in the GitHub repository product-on-purpose/thinking-framework-skills (15 stars, last pushed today), licensed Apache-2.0. It adds 126 tokens to every session and 1,806 once invoked, about $0.0006 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-30.

Related

Other skills, from other repositories

ops-demo

CocoOps demo mode activator — populates .cocoplus/ops/demo/ with realistic mock data and sets cocoplus.toml [demo] enabled = true. Invoked via $ops demo.

Snowflake-Labs/cocoplus · 46 tokens

add-analytics

Add Google Analytics 4 tracking to any project. Detects framework, adds tracking code, sets up events, and configures privacy settings.

LeoYeAI/openclaw-master-skills · 32 tokens

agent-teams-simplify-and-harden

Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…

LeoYeAI/openclaw-master-skills · 115 tokens

acl-rule-analysis

Vendor-agnostic ACL and firewall rule analysis with shadowed rule detection, overly permissive rule identification, unused rule discovery, redundant rule flagging, and rule ordering optimization. Covers ACLs (Cisco/JunOS/EOS) and firewall policies (PAN-OS/FortiGate/CheckPoint).

LeoYeAI/openclaw-master-skills · 64 tokens

agent-team-orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4)…

LeoYeAI/openclaw-master-skills · 102 tokens

agent-bom-enforce

Enforce security policies on MCP tool calls and block dangerous operations at runtime. Use when: "block risky calls", "apply policy", "proxy", "runtime protection", "policy enforcement", "intercept MCP calls".

LeoYeAI/openclaw-master-skills · 50 tokens