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-1-codebase-analysisgit clone --depth 1 https://github.com/Burly-Mingo/modernization-kitWhat 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.00435 |
| Opus 5 | $0.00000 | $0.00217 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
phase-1-codebase-analysis 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 2d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 1: Codebase Analysis
Read the actual source code and produce a factual technical assessment of each application. No recommendations yet — purely diagnostic.
For Each Application, Assess:
Architecture & Structure: Pattern, project structure, entry points, request flow, inter-app communication, third-party dependencies with version/EOL status.
Code Quality & Patterns: Language/framework versions, design patterns, separation of concerns, error handling, logging, configuration management.
Data Layer: Database tech/version/count, relationships, cross-DB dependencies, ORM/data access patterns, schema complexity, credential handling.
Security Posture: Password storage, auth/session management, SQL injection, XSS, CSRF, encryption, secrets management, compliance-relevant findings.
Business Logic Location: App code vs. stored procs vs. triggers vs. config tables. Quantify the ratio. Identify black-box components.
Deployment & Operations: Build process, deployment mechanism, environments, monitoring, backup/recovery.
7 R's Classification: For each app/component — Retain, Retire, Rehost, Replatform, Refactor, Rearchitect, or Rebuild. Tag each as [Tactical] or [Strategic] with justification.
Multi-App: Consolidated Assessment
After per-app assessments, produce CONSOLIDATED_ASSESSMENT.md: shared data sources, data ownership conflicts, overlapping business logic, hidden coupling, data consistency risks, blast radius of schema changes, consolidation opportunities, inter-app dependency map.
Deliverables
- ASSESSMENT.md per application (findings with evidence — file paths, code snippets, config values)
- CONSOLIDATED_ASSESSMENT.md for multi-app engagements
Scaling (Large Codebases)
- Prioritize: entry points, config, data access, auth, build/deploy (80/20 rule)
- Run static analysis tools first (SonarQube, Snyk), feed results for interpretation
- Consider vector DB approach for semantic code search
Human Checkpoint
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.
- 2d ago First seen · 39 lines · 0 tokens per session scan A 7f62dbc9b5c6
phase-1-codebase-analysis 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 435 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].