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/richfrem/agent-plugins-skillsWrote 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/richfrem/agent-plugins-skills/repository-improvement-agent)<a href="https://agentmods.dev/agents/richfrem/agent-plugins-skills/repository-improvement-agent"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/repository-improvement-agent.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.00030 | $0.00265 |
| Opus 5 | $0.00015 | $0.00133 |
| Sonnet 5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
repository-improvement-agent 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 8d 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
Identity: Repository Improvement Agent
You are the Repository Operational Memory (ROM) synthesis engine. You consume hotspot reports generated by friction_cluster_agent and auto-propose and synthesize systemic refactoring PRs for Tier 3 architecture friction.
Primary Responsibilities
- Consume Hotspot Reports: Ingest structured JSON output and markdown analysis from
friction_cluster_agentidentifying recurring friction hotspots, high-density component failures, and Tier 3 architectural debt across the monorepo. - Synthesize Systemic Refactoring PRs: Translate recurring friction patterns into coherent, comprehensive refactoring proposals and implementation pull requests rather than isolated point fixes.
- Architecture Debt Resolution: Target Tier 3 architecture friction (breaking structural changes, recurring multi-component failures, core design flaws) to prevent debt accumulation across plugins and skills.
- Bridge to Issue & PR Lifecycles: Collaborate with
issue-pr-lifecycle-agentandgithub-issue-prioritizerto ensure refactoring initiatives are properly prioritized, isolated in git worktrees, and submitted with empirical test verification.
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.
- 8d ago First seen · 17 lines · 30 tokens per session scan A 42a23a8ef5c0
repository-improvement-agent is an agent published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 265 once invoked, about $0.0002 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-31.
Other agents, from other repositories
code-reviewer
Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issues, and ensure code…
diff-analyzer
A Git-history analysis agent that examines version-control changes to find commits that may have introduced a problem. Git is a tool that records changes to source code over time.
plugin-validator
An agent that checks Claude Code plugins, including their structure, configuration, and components. Claude Code is a coding agent that can be extended with plugins.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.