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/burly-mingo/modernization-kit/phase-0-discoverygit 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-0-discovery)<a href="https://agentmods.dev/commands/burly-mingo/modernization-kit/phase-0-discovery"><img src="https://agentmods.dev/badge/commands/burly-mingo/modernization-kit/phase-0-discovery.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.00000 | $0.00473 |
| Opus 5 | $0.00000 | $0.00236 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
phase-0-discovery 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 5d 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 0: Discovery Interview
Understand the organization, its industry, its constraints, and its goals before touching any code. Present these questions conversationally, not as a checklist. Follow up based on answers.
Opening
I'm going to help you build a comprehensive modernization plan for your legacy application(s). Before I look at any code, I need to understand your organization, your constraints, and what you're trying to achieve. I'll ask questions in groups — answer what you can, and say "I don't know" for anything you're unsure about.
Question Groups
1. Organization & Industry: Core business, industry, employee count, IT headcount, locations, cloud accounts, cloud vs. on-prem preference, IT budget range.
2. Regulatory & Compliance: Identify all applicable frameworks (HIPAA, PCI-DSS, SOX, ITAR, FERPA, GLBA, CMMC, FedRAMP, GDPR, CCPA, NRC, FDA 21 CFR Part 11, SOC 2, gaming regulations). Compliance team? Recent audits? Data residency? Classified data?
3. Current Applications: For each app — name, purpose, users, age, tech stack, database(s), deployment. Inter-app communication? Dependent systems? Upstream dependencies?
4. Pain Points: Top 3-5 daily frustrations. Manual workarounds. Excel exports. Deployment process. Rollback capability. Backup status. Security incidents. Requested features.
5. People & Knowledge: Original developers available? Maintenance team size/skills? Documentation? Institutional knowledge? Modern tech experience? AI-assisted dev stance? Open-source policy?
6. Existing Infrastructure: Compute (servers, VMs, hypervisors, utilization, GPUs). Storage (SAN, NAS, capacity, backups). Networking (bandwidth, load balancers, firewalls, VPN). Licensing (costs, enterprise agreements, underutilized). Cloud (accounts, usage, spend, credits).
7. Goals & Constraints: Modernization driver. Success criteria. Timeline. Budget. Acceptable downtime. Technology mandates. Upcoming deadlines.
Deliverable
DISCOVERY_SUMMARY.md — all answers, applicable regulatory frameworks, known constraints, areas needing more information.
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.
- 5d ago First seen · 32 lines · 0 tokens per session scan A c10a367e1ee6
phase-0-discovery 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 473 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].