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 ChipAlexandru/strategy-consultant --skill problem-definitiongit clone --depth 1 https://github.com/ChipAlexandru/strategy-consultantWrote 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/chipalexandru/strategy-consultant/problem-definition)<a href="https://agentmods.dev/skills/chipalexandru/strategy-consultant/problem-definition"><img src="https://agentmods.dev/badge/skills/chipalexandru/strategy-consultant/problem-definition.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.00106 | $0.02474 |
| Opus 5 | $0.00053 | $0.01237 |
| Sonnet 5 | $0.00021 | $0.00495 |
| Haiku 4.5 | $0.00011 | $0.00247 |
Grade A, and why
problem-definition 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 8d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Problem Definition
Take the client situation — however vague or sprawling — and distill it into a problem statement sharp enough to drive analysis.
Routing Check (run BEFORE any other step)
This skill is Phase 1 of the engagement. There is no upstream phase to gate on for fresh runs, so this is not a hard upstream preflight gate (unlike research, sense-check, synthesis, client-report, etc.) — it is a routing check that confirms the skill is being entered through a legitimate path and that workspace ownership is correctly attributed to engagement-manager.
Before drafting anything, determine which case applies:
Case (a) — Fresh /engagement Phase 1 invocation. The user has just started a new engagement. engagement-manager owns workspace creation and initial state setup; it will create ./engagements/<slug>-<date>/ and initialize engagement-state.json during or immediately after this phase. Proceed normally with Steps 1–7 below. Do NOT create the workspace folder or write engagement-state.json from inside this skill — that is engagement-manager's responsibility. This skill produces problem-definition artifacts (problem-statement.md, client-question-checklist.md, precision-anchor.md, source-material-extraction-log.md) and engagement-manager places them in the correct workspace and registers them in state.
Case (b) — /define-problem continuation invocation. The user has invoked the continuation command to refine an existing engagement's problem definition. Before proceeding, verify that an active workspace exists:
./engagements/<slug>-<date>/engagement-state.jsonis present, OR- legacy
./engagement/precision-anchor.mdis present (v1.4.0 backward-compatible fallback).
If neither is present, STOP. Do not proceed with Steps 1–7. Do not create a workspace from inside this skill. Report to the user: "No active engagement workspace found. Use /engagement <topic> to start a new engagement — it will create the workspace and route into problem-definition automatically." Then route control back to engagement-manager.
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.
- 8d ago First seen · 150 lines · 106 tokens per session scan A 012d8ff3a8ba
problem-definition is a skill published in the GitHub repository ChipAlexandru/strategy-consultant (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 106 tokens to every session and 2,474 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…