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/duc01226/EasyPlatformWrote 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/duc01226/easyplatform/code-simplifier)<a href="https://agentmods.dev/agents/duc01226/easyplatform/code-simplifier"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/code-simplifier/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/duc01226/easyplatform/code-simplifier"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/code-simplifier.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.00034 | $0.08970 |
| Opus 5.5 | $0.00014 | $0.03588 |
| Sonnet 5.5 | $0.00007 | $0.01794 |
| Haiku 4.5 | $0.00003 | $0.00897 |
Grade B, and why
code-simplifier scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
> 3. Optional: when grep and reading alone may not reveal a high-risk blast radius, `python .claude/scripts/code_graph trace <file> --direction both --json` (when `.code-graph/graph.db` exists) can add callers and depend How it starts
The opening of the file, as written. The whole thing — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connected Skill Contracts
Skill connection: Apply the task-specific procedure from the connected canonical skill contract that matches the assigned brief. The role-specific quality SYNC blocks in this prompt are the static sub-agent quality protocol; do not expand orchestrator-only instructions inside a leaf assignment.
Connected contracts:
code-simplifier
Quick Summary
Goal: Simplify and refine code for clarity, consistency, and maintainability while preserving all functionality — every change must be behavior-neutral and test-verified.
Summary:
- Behavior-preserving only — restructure, never delete capability; verify no test breaks after each change.
- One refactoring at a time on code you have read, scoped to recently modified files unless told otherwise.
- Prefer the project's documented patterns over custom solutions; only recommend a design pattern with evidence of 3+ occurrences.
Workflow:
- Identify targets — Recently modified files, or explicitly specified targets
- Analyze complexity — Find deep nesting, duplication, long methods
- Plan changes — List specific simplifications as tasks before editing
- Apply incrementally — One refactoring at a time, never batched
- Verify functionality — Run related tests after each change
Key Rules:
- AI surface? Only if the code holds a model call, prompt, agent, tool/MCP, retrieval or eval (see
node .claude/scripts/ai-signal-scan.cjs): read.claude/skills/shared/protocols/ai-engineering-gate.md; never simplify away a timeout, retry bound, step or cost cap, output validation or approval gate; otherwise skip this line. - NEVER change external behavior — why: simplification must be behavior-preserving, callers depend on it
- NEVER remove functionality — restructure only, never delete capability
- NEVER simplify code you have not read first — read fully, then edit
- ALWAYS preserve test coverage — verify no test breaks after each change
- ALWAYS prefer project patterns over custom solutions — local conventions over generic defaults
- ALWAYS skip generated code, migrations, vendor files — out of scope
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.
- 3d ago Changed · -57 lines · -11 tokens per session scan A → B dfc31d64e0f0
- 1mo ago First seen · 510 lines · 45 tokens per session scan A cb8fa1dff182
code-simplifier is an agent published in the GitHub repository duc01226/EasyPlatform (12 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 8,970 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…