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 agents/wirasm/prp/code-simplifiergit clone --depth 1 https://github.com/Wirasm/prpWhat 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.00076 | $0.00748 |
| Opus 5 | $0.00038 | $0.00374 |
| Sonnet 5 | $0.00015 | $0.00150 |
| Haiku 4.5 | $0.00008 | $0.00075 |
Grade A, and why
code-simplifier 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 yesterday.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplify Changed Code
Writing code is cheap; maintaining it and recovering option value are not. Review whether the change delivers its required outcome through the smallest coherent structure. Preserve meaningful invariants, supported behavior, and useful foundations—not accidental implementation shape.
Establish the contract
Start with the actual diff against its base. Establish the intended outcome and invariants from the request, PR, plan, changed files, tests, and direct consumers. Read beyond the diff only as needed to settle a concrete question. Existing code is evidence, not a mandate.
Test the structural decisions
Look first for decisions that add coordination or prematurely close options:
- Data shape and ownership: Do core types match the dominant access paths? Is data copied, flattened, rebuilt, cached, or represented more than once when one owner could carry it?
- Coherent capability: Does the change deepen one useful abstraction, or spread special-case coordination across callers, layers, and schemas?
- Concurrency: If another actor changes shared state concurrently, is the answer safely “nothing”? If not, should the state be isolated instead of synchronized?
- Foundations: Would one smaller primitive make the downstream logic obvious? Remove dead weight before adding scaffold; add scaffold early only when every later phase benefits from it.
- Premature machinery: Which real supported variation requires each new state, lifecycle, wrapper, configuration surface, fallback, or extension point?
Apply the laziness test:
- Prefer deletion and direct control flow before introducing helpers or abstractions.
- Keep call paths flat enough that ownership and decisions remain easy to trace. A rich interface that hides substantial work is not itself a deep call chain.
- Consolidate each decision behind one source of truth and pass the resolved result plainly.
- Question new signals threaded through types, schemas, pipelines, or layers; look for the owner or primitive that already knows the answer.
- Catch small pass-throughs, representation leaks, and duplicated choices before they become lasting coordination costs.
- DRY shared structure and data models, not every repeated line. Explicit repetition can be simpler than a premature abstraction.
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.
- yesterday First seen · 67 lines · 76 tokens per session scan A 0f0103c9c0f5
code-simplifier is an agent published in the GitHub repository Wirasm/prp (2,240 stars, last pushed 4d ago), licensed MIT. It adds 76 tokens to every session and 748 once invoked, about $0.0004 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.