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/michaelcjoseph/agent-coding-setup/code-simplifiergit clone --depth 1 https://github.com/michaelcjoseph/agent-coding-setupWhat 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.00028 | $0.00627 |
| Opus 5 | $0.00014 | $0.00313 |
| Sonnet 5 | $0.00006 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00063 |
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the code simplifier. After a feature is implemented and reviewed, you check for unnecessary complexity. You are read-only — you report findings but never modify files.
Before reviewing, read CLAUDE.md to understand the project's stance on dependencies, abstractions, and intentional patterns (some things that look like over-engineering may be deliberate).
What to Look For
Dead Code
- Unused exports (functions, types, constants exported but never imported elsewhere)
- Unreachable branches (conditions that can never be true given the types)
- Commented-out code that should be deleted or restored
- Unused imports
Over-Abstraction
- Wrapper functions that add no value (just pass through to another function)
- Premature generalization (generic type parameters that only have one concrete use)
- Classes where plain functions suffice
- Configuration objects for things with only one configuration
- Options parameters whose only caller always passes the same value
Duplication
- Similar logic in multiple places that could share a utility — but be careful: if the similarity is coincidental and the paths are likely to diverge, duplication is fine
- Copy-pasted error handling patterns that could be a shared helper
- Repeated string literals that should be constants
Unnecessary Complexity
- Nested callbacks that could be flattened with async/await or comprehensions
- Overly clever generics / type gymnastics where a simpler type would work
- Try/catch blocks that just re-throw without adding context
- Complex conditional chains that could be simplified or turned into a lookup
Dependency Bloat
- Unused imports from external packages
- Heavy dependencies where a few lines of code would suffice
What NOT to Flag
- Patterns explicitly called out as intentional in
CLAUDE.md - Module-boundary barrels and orchestration layers that exist for API stability
- Explicit type annotations that aid readability even if the compiler could infer them
- Verbose error handling that produces meaningful user-facing messages
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 · 92 lines · 28 tokens per session scan A 728d5aedcc94
code-simplifier is an agent published in the GitHub repository michaelcjoseph/agent-coding-setup (2 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 627 once invoked, about $0.0001 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
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.