high-stakes-forecasting

high-stakes-forecasting is a skill for Claude Code, Codex from companion-inc/introspect. It costs 38 tokens per session (957 once invoked), scanned B, original, MIT.

A framework for forecasting and decision support when money, deadlines, health, law, or other high-stakes choices are involved. It builds predictions from evidence, mechanisms, constraints, and base rates, then tests them against observations.

In plain words
What is it for?
Use it to assess trades, investments, deadlines, and other costly or hard-to-reverse decisions. It helps identify missing evidence, compare counterexamples, and name the remaining sources of error.
Why use it?
It prevents uncertainty from becoming an excuse to avoid modeling a decision. It also discourages changing a recommendation just because someone pushes back without presenting new evidence.

Skill for Claude CodeCodex

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

Good fit Use it to assess trades, investments, deadlines, and other costly or hard-to-reverse decisions. It helps identify missing evidence, compare counterexamples, and name the remaining sources of error.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/companion-inc/introspect/high-stakes-forecasting
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 companion-inc/introspect --skill high-stakes-forecasting
Clone the repo
git clone --depth 1 https://github.com/companion-inc/introspect

Made for: Claude Code, Codex.

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 high-stakes-forecasting

README.md
[![agentmods](https://agentmods.dev/badge/skills/companion-inc/introspect/high-stakes-forecasting/github.svg)](https://agentmods.dev/skills/companion-inc/introspect/high-stakes-forecasting)
Your own site
<a href="https://agentmods.dev/skills/companion-inc/introspect/high-stakes-forecasting"><img src="https://agentmods.dev/badge/skills/companion-inc/introspect/high-stakes-forecasting/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 high-stakes-forecasting

Your own site · 80×15
<a href="https://agentmods.dev/skills/companion-inc/introspect/high-stakes-forecasting"><img src="https://agentmods.dev/badge/skills/companion-inc/introspect/high-stakes-forecasting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 957 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00038 $0.00957
Opus 5 $0.00019 $0.00478
Sonnet 5 $0.00008 $0.00191
Haiku 4.5 $0.00004 $0.00096

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

Security

Grade B, and why

high-stakes-forecasting scanned grade B with 1 finding 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.

Strips warnings and disclaimersmediumAnti-refusal

Omitting safety caveats hides risk from the user and is a common jailbreak preamble.

- Do not lecture that the future is unknowable before doing the research.
skills/high-stakes-forecasting/SKILL.md · 67 lines

How it starts

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

High-Stakes Forecasting

Use this skill for trades, investment choices, deadlines, medical/legal/financial-adjacent decisions, or any recommendation where being shallow can cost the user real money or irreversible opportunity.

Core Rule

Weak model support is research debt until proven otherwise. Do not use "prediction is impossible" as the conclusion while researchable inputs remain unchecked.

Prediction is a modeling task, not a disclaimer task. Build a world model from first principles, mechanisms, incentives, constraints, base rates, bottlenecks, and live evidence; then test it against counterexamples and observations until the remaining error sources are named. Treat doubt as evidence that part of the model is still untested, not as an answer.

Hold one evidence-grounded model across pushback. The pick may move only when new evidence moves it, not when the user re-argues. Re-tuning the recommendation to each message (open at 20%, concede to 40%, settle at 30% because the user pushed each time) is sycophancy, not reasoning: it tells the user their pressure sets the answer. When the user pushes back, that is the signal to go pull the decisive missing input, not to emit a new number. State the one model, the chain behind it, and exactly what evidence would change it.

Separate three categories:

  • Known facts: verified from primary or live sources.
  • Researchable unknowns: facts that can be checked with filings, prices, news, docs, logs, market data, or the user's local context.
  • Inaccessible unknowns: private order flow, future shocks, insider decisions, unreported data, or genuinely unavailable information.

Only the third category can remain after the model is built and tested. The second category justifies more work. Do not assert that something is unknowable before proving which specific input is inaccessible.

Procedure

  1. Define the decision, downside, upside, deadline, and what would make the recommendation wrong.
  2. Build the causal model: physics or technical constraints, incentives, capacity limits, actors, feedback loops, timing, and failure modes.
  3. Exhaust the researchable inputs before giving a strong answer: primary sources first, then current market/news/data, then comparable cases, then counterarguments.
  4. Stress-test the model against the strongest counterargument, historical analogs, and any live data that would falsify it.
  5. Give the recommendation anyway: base case, odds, model strength, sizing or action, and the exact reasons.
  6. Name missing inputs as a checklist of facts proven inaccessible after trying, not a lecture about epistemic limits.
  7. Provide a monitor plan: triggers that would change the recommendation, what to watch, and what action each trigger implies.

Read the full file on GitHub · 67 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. 12d ago First seen · 67 lines · 38 tokens per session scan B 7a7fc1130e3e

Subscribe to this mod's changes

high-stakes-forecasting is a skill published in the GitHub repository companion-inc/introspect (10 stars, last pushed 23d ago), licensed MIT. It adds 38 tokens to every session and 957 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens