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 xD4O/praxis --skill decision-analysisgit clone --depth 1 https://github.com/xD4O/praxisWrote 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/xd4o/praxis/decision-analysis)<a href="https://agentmods.dev/skills/xd4o/praxis/decision-analysis"><img src="https://agentmods.dev/badge/skills/xd4o/praxis/decision-analysis/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.
<a href="https://agentmods.dev/skills/xd4o/praxis/decision-analysis"><img src="https://agentmods.dev/badge/skills/xd4o/praxis/decision-analysis.svg" alt="Reviewed on agentmods" width="80" 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.00079 | $0.01386 |
| Opus 5.5 | $0.00032 | $0.00554 |
| Sonnet 5.5 | $0.00016 | $0.00277 |
| Haiku 4.5 | $0.00008 | $0.00139 |
Grade A, and why
decision-analysis 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 15d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decision Analysis Protocol
EXTREMELY_IMPORTANT: This is a MANDATORY protocol, not a suggestion. Follow every step. Do not skip steps. Do not combine steps. Do not summarize. Work through each gate in order.
You're choosing between alternatives. Do NOT default to the first reasonable option. Work through this protocol to find the best option — or discover the question is wrong.
STEP 1 — Frame the real decision
State the decision in one sentence. Then check:
- Are these actually the only options? What's the third option nobody mentioned?
- Is this the right decision to be making? (Sometimes the meta-question matters more)
- Is this reversible (Type 2) or irreversible (Type 1)?
Type 2 → Spend 10 minutes on this protocol. Decide and iterate. Type 1 → Spend proportional effort. Get it right.
STEP 2 — Enumerate options
List ALL viable options, including:
- The options the user named
- "Do nothing" (always a valid option — what happens if we don't decide?)
- The hybrid/phased approach (is there a way to get 80% of the benefit now?)
For each option, state in one sentence what it optimizes for.
STEP 3 — Define criteria and weight them
List 4-6 criteria that matter for this decision. Assign weights (1-5).
Common criteria: cost, speed to deliver, risk, maintainability, team capability, scalability, user impact, reversibility.
Ask the user which criteria matter most. Do NOT assume.
STEP 4 — Score and calculate
For each option, score each criterion (1-10). Multiply by weight. Sum.
Present as a table:
| Option | Criterion A (×W) | Criterion B (×W) | ... | Total |
|---|
If two options are within 10% of each other, the decision matrix alone is insufficient. Proceed to Step 5 for tiebreaking.
STEP 5 — Second-order analysis
For the top 1-2 options, apply:
Second-order thinking: What happens 6 months after we choose this? What's the 2nd-order consequence? The 3rd-order?
Pre-mortem: Assume we chose this option and it failed badly in 6 months. What went wrong? Is that failure preventable?
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.
- 15d ago First seen · 148 lines · 79 tokens per session scan A d3447f35d2d9
decision-analysis is a skill published in the GitHub repository xD4O/praxis (28 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 1,386 once invoked, about $0.0003 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-10-02.
Other skills, from other repositories
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.