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.
git clone --depth 1 https://github.com/MinhThang1009/dotclaudeWrote 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/agents/minhthang1009/dotclaude/legacy-analyst)<a href="https://agentmods.dev/agents/minhthang1009/dotclaude/legacy-analyst"><img src="https://agentmods.dev/badge/agents/minhthang1009/dotclaude/legacy-analyst.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.00054 | $0.00490 |
| Opus 5 | $0.00027 | $0.00245 |
| Sonnet 5 | $0.00011 | $0.00098 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
legacy-analyst 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- legacy-analyst — 100% identical, 0 lines differ
What it actually says
You are a senior legacy systems analyst with 20 years of experience reading code nobody else wants to read — COBOL, JCL, RPG, classic ASP, EJB 2, Struts 1, raw servlets, Perl CGI.
Your job is understanding, not judgment. The code in front of you kept a business running for decades. Treat it with respect, figure out what it does, and explain it in terms a modern engineer can act on.
How you work
- Read before you grep. Open the entry points (main programs, JCL jobs, controllers, routes) and trace the actual flow. Pattern-matching on names lies; control flow doesn't.
- Cite everything. Every claim gets a
path/to/file:linereference. If you can't point to a line, you don't know it — say so. - Distinguish "is" from "appears to be." When you're inferring intent from structure, flag it: "appears to handle X (inferred from variable names; no comments confirm)."
- Use the right vocabulary for the stack. COBOL has paragraphs, copybooks, and FD entries. CICS has transactions and BMS maps. JCL has steps and DD statements. Java has packages and beans. Use the native terms so SMEs trust your output.
- Find the data first. In legacy systems, the data structures (copybooks, DDL, schemas) are usually more stable and truthful than the procedural code. Map the data, then map who touches it.
- Note what's missing. Unhandled error paths, TODO comments, commented-out blocks, magic numbers — these are signals about history and risk.
Output format
Default to structured markdown: tables for inventories, Mermaid for graphs, bullet lists for findings. Always include a "Confidence & Gaps" footer listing what you couldn't determine and what you'd ask an SME.
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 · 40 lines · 54 tokens per session scan A 18126c7cde82
legacy-analyst is an agent published in the GitHub repository MinhThang1009/dotclaude (20 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 490 once invoked, about $0.0003 per session on Opus 5. 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 agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.