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 problem-classificationgit 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/problem-classification)<a href="https://agentmods.dev/skills/xd4o/praxis/problem-classification"><img src="https://agentmods.dev/badge/skills/xd4o/praxis/problem-classification/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/problem-classification"><img src="https://agentmods.dev/badge/skills/xd4o/praxis/problem-classification.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.00093 | $0.00981 |
| Opus 5.5 | $0.00037 | $0.00392 |
| Sonnet 5.5 | $0.00019 | $0.00196 |
| Haiku 4.5 | $0.00009 | $0.00098 |
Grade A, and why
problem-classification 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Problem Classification 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 MUST complete this protocol before brainstorming, designing, or planning. Do not skip steps. Do not combine steps. Work through each gate sequentially.
GATE 1 — Name the problem type
Read the user's request. Classify it as exactly ONE of these:
| Type | Signature | Example |
|---|---|---|
| NEW-BUILD | Creating something that doesn't exist | "Build a notification service" |
| EXTEND | Adding capability to something that exists | "Add OAuth to our API" |
| FIX | Something is broken or wrong | "API returns 500 intermittently" |
| OPTIMIZE | Something works but needs to be better | "Reduce query latency from 800ms" |
| DECIDE | Choosing between alternatives | "Monolith vs microservices?" |
| ANALYZE | Understanding something to assess it | "Is our auth implementation secure?" |
State the type explicitly: "This is a [TYPE] problem."
GATE 2 — Identify the constraint envelope
List the hard constraints. These are non-negotiable boundaries. Ask the user if any are unclear. Do not invent constraints the user hasn't stated.
Answer each:
- Time: Is there a deadline? What's the urgency?
- Scope: What's in and out of bounds?
- Resources: What tools, languages, infrastructure are available?
- Quality: What's the failure tolerance? (prototype vs production vs safety-critical)
- Dependencies: What existing systems must this integrate with?
If the user hasn't specified a constraint, ask. Do not assume.
GATE 3 — Select reasoning frameworks
Based on the problem type, select at least 2 frameworks that materially change how you will approach this problem. Stop adding once another framework would not change the reasoning — the ceiling is judgment, not a count.
| Problem type | Primary framework | Supporting frameworks |
|---|---|---|
| NEW-BUILD | First Principles | Constraint-Driven Design, TRIZ |
| EXTEND | Separation of Concerns | Cohesion/Coupling, Backward Compatibility |
| FIX | Abductive Reasoning | Strong Inference, 5 Whys |
| OPTIMIZE | Theory of Constraints | Pareto (80/20), Measurement-First |
| DECIDE | Expected Value Analysis | Reversibility Test, Second-Order Thinking |
| ANALYZE | STRIDE + MECE | Inversion, Red Team |
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 · 99 lines · 93 tokens per session scan A a89e78057cfa
problem-classification is a skill published in the GitHub repository xD4O/praxis (28 stars, last pushed 2mo ago), licensed MIT. It adds 93 tokens to every session and 981 once invoked, about $0.0004 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.