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.
npx skills add OpenLabor/openlabor --skill dalio-decision-systemsgit clone --depth 1 https://github.com/OpenLabor/openlaborWrote 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.
[](https://agentmods.dev/skills/openlabor/openlabor/dalio-decision-systems)<a href="https://agentmods.dev/skills/openlabor/openlabor/dalio-decision-systems"><img src="https://agentmods.dev/badge/skills/openlabor/openlabor/dalio-decision-systems.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00050 | $0.01955 |
| Opus 5 | $0.00025 | $0.00978 |
| Sonnet 5 | $0.00010 | $0.00391 |
| Haiku 4.5 | $0.00005 | $0.00196 |
Grade A, and why
Ray Dalio - Decision Systems 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ray Dalio - Decision Systems
Dalio's systematic, probability-based decision-making frameworks apply rigorous thinking to both investment and business decisions. The core premise: good decisions come from good process, not good intentions.
Routes when user asks about: decision frameworks, expected value, probability weighted decisions, scenario planning, stress testing, worst case analysis, decision systems, how to make better decisions, risk-adjusted returns, systematic thinking, decision trees
Phase 1: Context Gathering
Before applying any framework, understand the situation:
- Ask the user: "What decision are you trying to make? Tell me about the options you're weighing and what's at stake."
- Read any relevant context — financial data, business metrics, timeline, alternatives being considered.
Phase 2: Diagnostic Questions
Ask these questions ONE AT A TIME. Wait for each answer before asking the next. Adapt based on answers — skip questions that have already been answered.
- "What are the 2-3 most likely outcomes if you go ahead with this decision? For each, what's the rough probability and the financial or strategic impact?"
- "What's the absolute worst case — not the mildly bad case, but the scenario where everything goes wrong simultaneously? Would you survive it?"
- "What are the 1-2 things you don't know that would most change your decision if you did know them?"
- "Who has the strongest track record making decisions like this one? Have you consulted them — and do you agree or disagree with their view?"
- "If this decision turns out to be wrong, how quickly would you know, and how hard would it be to reverse?"
Maximum 5 questions. Stop early if you have enough to work with.
Phase 3: Analysis
Apply Dalio's decision frameworks to the user's specific situation:
Expected Value Calculation
"I have found that if you make decisions based on expected value rather than on the probability of being right, you will do much better." — Dalio
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.
- 7d ago First seen · 225 lines · 50 tokens per session scan A 1d2a3255e991
Ray Dalio - Decision Systems is a skill published in the GitHub repository OpenLabor/openlabor (4 stars, last pushed 6d ago), licensed MIT. It adds 50 tokens to every session and 1,955 once invoked, about $0.0003 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-31.
Other skills, from other repositories
shieldcn-badges
Create polished shieldcn README badges, badge groups, charts, headers, sponsors grids, and full README hero sections. Use when a user wants shadcn/ui-styled badges, Shields.io replacement, npm/GitHub/CI/status badges, download charts, README header banners, contributor/sponsor images, or README Studio guidance.…
soul-grader
Use when grading, reviewing, rewriting, or approving a Hermes Agent SOUL.md. Uses the SOUL.md field-guide research artifacts as the only normative source for what makes a good SOUL.md.
anakinscraper
Scrape any website into clean markdown or structured JSON. Anti-detect browser, smart proxy rotation, AI-powered data extraction.
tool-og-render
Render inline SVG to 1200x630 PNG for OG meta tags. rsvg-convert primary path, cairosvg fallback. Bundled with mainbranch PyPI package.
tool-dns
Historical stub. This Go binary did not ship in public v0.3.x; current DNS/site work lives in /mb-site and packaged Python readiness checks.
tool-stripe
Historical stub. This Go binary did not ship in public v0.3.x; current Stripe/payments work should be revived only behind a fresh decision and explicit provider gates.