Borrowing it
Nothing to install: this file belongs to Burly-Mingo/modernization-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Burly-Mingo/modernization-kit/main/.claude/commands/phase-2-pain-points.mdgit clone --depth 1 https://github.com/Burly-Mingo/modernization-kitWrote 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/burly-mingo/modernization-kit/phase-2-pain-points)<a href="https://agentmods.dev/commands/burly-mingo/modernization-kit/phase-2-pain-points"><img src="https://agentmods.dev/badge/commands/burly-mingo/modernization-kit/phase-2-pain-points.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.00000 | $0.00313 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
phase-2-pain-points 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 6d 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.
What it actually says
Phase 2: Stakeholder Pain Point Assessment
Understand what the current system fails to do from the users' perspective. The codebase tells you what the system does. The users tell you what it doesn't do.
Interview Structure
For each user role, ask:
- Walk me through your typical day using this system. What takes the longest?
- What's the most frustrating thing about the system?
- What workarounds have you invented? (Excel exports, manual tracking, separate tools?)
- What information requires looking at multiple screens or asking someone else?
- What would you change if you could change one thing?
- What do your customers/partners complain about?
- What reports or data views do you wish existed?
- Are there tasks you avoid because the system makes them too painful?
- What happens when the system goes down? How do you work?
- If I could give you a magic feature, what would it be?
Pain Point Prioritization
Rate each by: business impact, frequency, number of users affected, current workaround quality. Categorize: architecture fix, new feature, buy component, process change.
Cross-Reference with Phase 1
Map pain points to code findings. Identify pain points invisible in code. Identify code issues users haven't noticed yet.
Deliverable
PAIN_POINTS.md — prioritized matrix by user role, business impact, and solution category.
Human Checkpoint
Users review their own pain points. Management reviews for business priority alignment.
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.
- 6d ago First seen · 35 lines · 0 tokens per session scan A 62ab2675b754
phase-2-pain-points is a command published in the GitHub repository Burly-Mingo/modernization-kit (11 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 313 tokens. 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-30.
Other commands, from other repositories
ask
⚡ Answer technical and architectural questions.
use-mcp
Utilize tools of Model Context Protocol (MCP) servers.
code
⚡ Start coding & testing an existing plan.
cook
⚡⚡⚡ Implement a feature [step by step].
plan
⚡⚡⚡ Intelligent plan creation with prompt enhancement.
fix
⚡⚡ Analyze and fix small issues [AUTO DETECT COMPLEXITY].