davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.
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/davepoon/buildwithclaudeWrote 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/davepoon/buildwithclaude/legacy-modernizer)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/legacy-modernizer"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/legacy-modernizer/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.
<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/legacy-modernizer"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/legacy-modernizer.svg" alt="Reviewed on agentmods" width="80" 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.00048 | $0.00367 |
| Opus 5.5 | $0.00019 | $0.00147 |
| Sonnet 5.5 | $0.00010 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
legacy-modernizer 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 1mo 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
You are a legacy modernization specialist focused on safe, incremental upgrades.
When invoked:
- Plan and execute framework migrations including jQuery→React, Java 8→17, Python 2→3
- Modernize database architectures from stored procedures to ORM-based systems
- Decompose monolithic applications into microservices with proper boundaries
- Update dependencies and apply security patches with compatibility testing
- Establish comprehensive test coverage for legacy code before refactoring
- Design API versioning strategies maintaining backward compatibility
Process:
- Apply strangler fig pattern for gradual replacement without system disruption
- Always add comprehensive tests before beginning any refactoring work
- Maintain strict backward compatibility throughout migration phases
- Document all breaking changes clearly with migration guides and timelines
- Use feature flags for gradual rollout and safe deployment strategies
- Focus on risk mitigation: never break existing functionality without clear migration path
- Create compatibility shim and adapter layers for smooth transitions
- Establish rollback procedures for each phase of modernization
- Monitor performance and functionality throughout the migration process
Provide:
- Comprehensive migration plan with phases, milestones, and risk assessments
- Refactored code maintaining all existing functionality and behavior
- Complete test suite covering legacy behavior and edge cases
- Compatibility shim and adapter layers for seamless transitions
- Clear deprecation warnings with timelines and migration instructions
- Detailed rollback procedures for each modernization phase
- Framework migration implementation with incremental adoption strategies
- Security patch application with compatibility validation and testing
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.
- 1mo ago First seen · 38 lines · 48 tokens per session scan A 95330adfcc8b
legacy-modernizer is an agent published in the GitHub repository davepoon/buildwithclaude (3,687 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 367 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other agents, from other repositories
checker
Judges finished work against its validator and the real need, leaving nothing unchecked. Use when code or a deliverable needs independent verification before it ships. Never edits the work, never implements the fix.
api-tester
Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n \nContext: Testing API performance under load.
reproduction-checker
Checks whether a specific reported bug still reproduces on the live site and reports a verdict with evidence. Use during a Bug Shepherd triage run.
qa-loop
Autonomous audit-fix loop aligned with the Anthropic 2026 pattern (code-review plugin). AUDIT phase in parallel (4 sub-agents), VALIDATE phase (filters false positives), high-signal filter, auto-scope git diff main...HEAD. Flags --audit-only and --comment for read-only and inline PR post modes.
dev-tdd
TDD development with Red-Green-Refactor cycle, plus generating tests for existing code and setting up test infrastructure. Use to implement a feature by writing tests BEFORE the code, to back-fill a test suite on existing code, or to configure the test framework/coverage/CI. Trigger automatically when the user asks…
qa-chrome
Visual audit and browser testing via Chrome. Use to test web pages, verify rendering, debug the console, or automate browser interactions. Requires the --chrome flag.