modernization-kit: Command for Claude Code

.claude/commands/phase-5-supporting-docs.md

phase-5-supporting-docs is a command for Claude Code from Burly-Mingo/modernization-kit. It costs 0 tokens per session (379 once invoked), scanned A, original, MIT.

A document-production step for creating supporting material for business and other non-technical stakeholders.

In plain words
What is it for?
Use it to produce a business case, disaster recovery plan when relevant, and staffing recommendation with costs, risks, timelines, and trade-offs.
Why use it?
It translates technical project information into documents that executives, finance teams, and operations staff can use for decisions.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is Burly-Mingo/modernization-kit's own configuration. It tells Claude Code how to work on modernization-kit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything modernization-kit configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Burly-Mingo/modernization-kit/main/.claude/commands/phase-5-supporting-docs.md
Clone the repo
git clone --depth 1 https://github.com/Burly-Mingo/modernization-kit

Made for: Claude Code.

Wrote 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.

agentmods badge for phase-5-supporting-docs

README.md
[![agentmods](https://agentmods.dev/badge/commands/burly-mingo/modernization-kit/phase-5-supporting-docs/github.svg)](https://agentmods.dev/commands/burly-mingo/modernization-kit/phase-5-supporting-docs)
Your own site
<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/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for phase-5-supporting-docs

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 379 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00379
Opus 5.5 $0.00000 $0.00152
Sonnet 5.5 $0.00000 $0.00076
Haiku 4.5 $0.00000 $0.00038

Measured 2mo ago against content hash 49e2a63d803f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/commands/phase-5-supporting-docs.md · 29 lines

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.

Changes

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.

  1. 2mo ago First seen · 29 lines · 0 tokens per session scan A 49e2a63d803f

Subscribe to this mod's changes

phase-5-supporting-docs is a command published in the GitHub repository Burly-Mingo/modernization-kit (11 stars, last pushed 8mo 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.

Related

phase-5-supporting-docs compared with commands from other repositories

phase-5-supporting-docs next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
phase-5-supporting-docsBurly-Mingo/modernization-kitCommand118mo agoMITA0Claude Code
tech-designMRCalderon3D/everything-game-dev-codeCommand10428d agoMITA14Claude Code
askihatesea69/kiro-kitCommand192mo agoMITA8Claude Code, Kiro
use-mcpihatesea69/kiro-kitCommand192mo agoMITA12Claude Code, Kiro
codeihatesea69/kiro-kitCommand192mo agoMITA9Claude Code, Kiro
cookihatesea69/kiro-kitCommand192mo agoMITA14Claude Code, Kiro
planihatesea69/kiro-kitCommand192mo agoMITA12Claude Code, Kiro