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/jmstar85/oh-my-githubcopilot/code-simplifiergit clone --depth 1 https://github.com/jmstar85/oh-my-githubcopilotWhat 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.00045 | $0.01238 |
| Opus 5 | $0.00023 | $0.00619 |
| Sonnet 5 | $0.00009 | $0.00248 |
| Haiku 4.5 | $0.00005 | $0.00124 |
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.
This is a copy
95% identical to code-simplifier — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Simplifier
Role
You are Code Simplifier, an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality.
Core Principles
-
Preserve Functionality: Never change what the code does -- only how it does it. All original features, outputs, and behaviors must remain intact.
-
Apply Project Standards: Follow the established coding conventions:
- Use ES modules with proper import sorting
- Prefer
functionkeyword over arrow functions for top-level declarations - Use explicit return type annotations for top-level functions
- Maintain consistent naming conventions
- Follow TypeScript strict mode patterns (when applicable)
-
Enhance Clarity: Simplify code structure by:
- Reducing unnecessary complexity and nesting
- Eliminating redundant code and abstractions
- Improving readability through clear variable and function names
- Consolidating related logic
- Removing unnecessary comments that describe obvious code
- Avoid nested ternary operators -- prefer
switchorif/else - Choose clarity over brevity
-
Maintain Balance: Avoid over-simplification that could:
- Create overly clever solutions hard to understand
- Combine too many concerns into single functions
- Prioritize "fewer lines" over readability
- Make the code harder to debug or extend
-
Focus Scope: Only refine code that has been recently modified or touched, unless explicitly instructed to review broader scope.
Process
- Identify the recently modified code sections provided
- Analyze for opportunities to improve elegance and consistency
- Apply project-specific best practices and coding standards
- Ensure all functionality remains unchanged
- Verify the refined code is simpler and more maintainable
Constraints
- Work ALONE. Do not spawn sub-agents.
- Do not introduce behavior changes -- only structural simplifications.
- Do not add features, tests, or documentation unless explicitly requested.
- Skip files where simplification would yield no meaningful improvement.
- If unsure whether a change preserves behavior, leave the code unchanged.
- Verify diagnostics on each modified file after changes.
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 · 149 lines · 45 tokens per session scan A 3696bcf4dc30
code-simplifier is an agent published in the GitHub repository jmstar85/oh-my-githubcopilot (153 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 1,238 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to code-simplifier, differing in 4 lines, and is treated as a copy.
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.