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-5-supporting-docsgit 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-5-supporting-docs)<a href="https://agentmods.dev/commands/burly-mingo/modernization-kit/phase-5-supporting-docs"><img src="https://agentmods.dev/badge/commands/burly-mingo/modernization-kit/phase-5-supporting-docs.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.00379 |
| Opus 5 | $0.00000 | $0.00189 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
phase-5-supporting-docs 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.
What it actually says
Phase 5: Supporting Documents
Produce documents for stakeholders beyond the technical team.
Documents
1. Business Case (BUSINESS_CASE.md): Executive summary (one page, non-technical, CFO/CEO readable). Problem statement in business terms. Proposed solution (high-level). Cost breakdown. ROI analysis (quantified). Timeline summary. Top 5 risks with mitigations. Recommendation. Translate technical benefits into business outcomes.
2. Disaster Recovery Plan (DISASTER_RECOVERY_PLAN.md, if applicable): Current state assessment. RPO/RTO targets. Backup strategy (what, where, how often, tested?). Failover architecture. Recovery runbooks. Testing schedule. DR infrastructure cost. Geographic/environmental risk.
3. Staffing Recommendation (STAFFING_RECOMMENDATION.md): Honest current team capacity assessment. ALL staffing models with trade-offs:
- Internal (existing): domain knowledge vs. pulls from maintenance
- New hire: full cost — salary + 25-40% benefits + $15K-$50K recruiting + 1-3 month onboarding. A "$150K developer" costs $195K-$240K/year fully loaded.
- Contract/consulting: rate × duration + procurement + knowledge transfer risk
- Hybrid: internal for domain + external for specialized skills
- Managed service: highest cost, lowest internal burden
Skills gap analysis. Skills matrix. Key person risk. Knowledge transfer plan. Post-modernization maintenance staffing.
4. Security Remediation Plan (SECURITY_REMEDIATION.md): Critical vulnerabilities to fix before modernization. Prioritized by severity/exploitability. Specific remediation steps. Effort estimates. Verification criteria.
Human Checkpoint
Each document reviewed by its target audience: business case → management/finance, DR → IT/ops, staffing → management/HR, security → IT/security.
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 · 29 lines · 0 tokens per session scan A 49e2a63d803f
phase-5-supporting-docs 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 379 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.
gdd
Create or update the Game Design Document for the current feature, system, or project.
tech-design
Create or update a technical design document for the selected feature or system.
use-mcp
Utilize tools of Model Context Protocol (MCP) servers.
code
⚡ Start coding & testing an existing plan.
cook
⚡⚡⚡ Implement a feature [step by step].