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 strategic-reasoninggit 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/strategic-reasoning)<a href="https://agentmods.dev/skills/xd4o/praxis/strategic-reasoning"><img src="https://agentmods.dev/badge/skills/xd4o/praxis/strategic-reasoning/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/strategic-reasoning"><img src="https://agentmods.dev/badge/skills/xd4o/praxis/strategic-reasoning.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.00075 | $0.00947 |
| Opus 5.5 | $0.00030 | $0.00379 |
| Sonnet 5.5 | $0.00015 | $0.00189 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
strategic-reasoning 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategic Reasoning 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.
This isn't a code problem — it's a strategy problem. Different tools.
STEP 1 — Clarify the real job
Ask: "What job is the user actually hiring this solution for?"
The stated goal is often not the real goal:
- "We need a dashboard" → Real job: "Convince the board we're growing"
- "Add feature X" → Real job: "Stop losing customers to competitor Y"
- "Rewrite in Rust" → Real job: "Our system can't handle next year's scale"
State the real job in one sentence. Confirm with the user.
STEP 2 — Situational assessment (SWOT)
Complete all four quadrants. Each must have 3+ items.
- Strengths (internal, positive): What advantages exist today?
- Weaknesses (internal, negative): What limitations constrain you?
- Opportunities (external, positive): What trends or gaps can you exploit?
- Threats (external, negative): What could undermine you?
Then cross-reference:
- How can strengths capture opportunities?
- How do weaknesses amplify threats?
- Which Strength+Opportunity pair is the highest-leverage play?
STEP 3 — Competitive landscape
If competitors or alternatives are relevant, map them:
- Who else solves this job? (direct competitors, substitutes, "do nothing")
- What do they do better? What do they do worse?
- Where is the uncontested space they don't occupy?
State the differentiation strategy in one sentence.
STEP 4 — Prioritize ruthlessly
If multiple initiatives are competing for resources, apply:
Impact vs effort matrix: For each initiative, estimate impact (1-10) and effort (1-10). Plot mentally. High impact + low effort = do first.
Constraint check: What's the bottleneck? Time, money, people, skill? Which initiatives are blocked by the same constraint? Resolve the constraint first, or accept that blocked initiatives won't happen.
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 · 107 lines · 75 tokens per session scan A 7c79bbeb547e
strategic-reasoning is a skill published in the GitHub repository xD4O/praxis (28 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 947 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.