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 agentmods add commands/chipalexandru/strategy-consultant/define-problemgit 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/commands/chipalexandru/strategy-consultant/define-problem)<a href="https://agentmods.dev/commands/chipalexandru/strategy-consultant/define-problem"><img src="https://agentmods.dev/badge/commands/chipalexandru/strategy-consultant/define-problem.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 | $0.00022 | $0.00498 |
| Opus 5 | $0.00011 | $0.00249 |
| Sonnet 5 | $0.00004 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
define-problem 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 4d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CONTINUATION COMMAND — do not use as a fresh entry point
This command continues an existing engagement. Before any other tool call:
- Check for an engagement workspace (
./engagements/<slug>-<date>/engagement-state.json, or — for legacy engagements —./engagement/precision-anchor.md). - If a workspace exists → continue from this phase using its state.
- If a workspace does NOT exist → STOP. Invoke /engagement instead. engagement-manager creates the workspace and routes to the correct starting phase, including this one if appropriate.
Do not attempt to run this phase cold. The workspace setup, slug, dating convention, and state file are owned by engagement-manager — reconstructing them here rebuilds the orchestrator piecemeal.
/define-problem — Problem Definition (continuation)
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Important: This plugin assists with strategic analysis and research but does not constitute professional consulting, financial, or legal advice. All outputs should be reviewed by qualified professionals before use in decision-making.
Resume problem-definition inside an active engagement — refining the problem statement, Precision Anchor, Client Question Checklist, and Deliverable Blueprint when the engagement-manager has routed back here.
Usage
/define-problem <business challenge or brief>
The argument is informational only — the authoritative scope and prior artifacts come from the active engagement workspace, not from the argument string.
If no engagement workspace exists, do not attempt to start one. Stop and route the user to /engagement.
Workflow
This command resumes the problem-definition skill inside an active engagement. The skill's preflight gate verifies that engagement-state.json exists. The detailed steps (raw extraction, targeted clarifying questions, problem-statement drafting, Deliverable Blueprint, stress-tests, Client Question Checklist, Precision Anchor) live in skills/problem-definition/SKILL.md. This command file does not duplicate them.
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.
- 4d ago First seen · 46 lines · 22 tokens per session scan A 091c6e7f5f43
define-problem is a command published in the GitHub repository ChipAlexandru/strategy-consultant (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 498 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.