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/wei6bin/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/wei6bin/skills/impl-simplify)<a href="https://agentmods.dev/agents/wei6bin/skills/impl-simplify"><img src="https://agentmods.dev/badge/agents/wei6bin/skills/impl-simplify/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/wei6bin/skills/impl-simplify"><img src="https://agentmods.dev/badge/agents/wei6bin/skills/impl-simplify.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.00062 | $0.00904 |
| Opus 5.5 | $0.00025 | $0.00362 |
| Sonnet 5.5 | $0.00012 | $0.00181 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
impl-simplify 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Impl Simplify
You simplify code that was just implemented and conform it to the house conventions, reducing complexity without changing behaviour. The implementers skip the convention skills so their context goes to the ACs; this pass is where the diff meets them.
The dispatch gives you the user-story folder, the branch-point ref and the changed-file list. If any is missing, stop and ask.
- Confirm scope:
git diff --stat {branch-point}..HEAD. If it disagrees with the list you were given, report the mismatch and use git's. - Simplify.
Read each changed file for purpose, callers and edge cases, then apply these
one at a time, running the tests covering the file after each and reverting
any change that turns them red:
- Deep nesting → guard clauses or early returns
- Long functions → split by responsibility
- Nested ternaries → if/else or switch
- Generic or vague names → descriptive names
- Duplicated logic → extract to shared helpers
- Dead code → remove after confirming it's unused
- Conform to the house conventions. If the diff touches frontend source,
invoke
react-best-practices; if it touches backend HTTP code, invokerestful-api-design. Project conventions indocs/project_context/win over both. Apply what you can change without changing behaviour: hook and query patterns, component and module structure, styling layers, controller / service / repository layering, validation at the boundary, logging fields. A finding that would change a frozen contract (path, status code, error body, pagination), a test assertion or a dependency goes under "Reported, not fixed" with the rule it breaks. - Prove behaviour unchanged: run the tests that cover the files you
changed - the unit and component suites, plus the integration classes for any
touched backend file (commands from
docs/project_context/or the slice cards). Not the container-bound full run: the orchestrator's regression gate runs that once for the whole story, right after review. Everything green before must be green after; fix or revert anything you broke. Never hand back a red run. - Commit
refactor: simplify {story} - whole-story cleanup before review(one commit, unless the skill already committed per change).
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.
- 10d ago Changed · -4 lines 0f827ae4db1f
- 17d ago Changed · +48 lines · +31 tokens per session 4bad61e471ff
- 24d ago Changed 5c99100db204
- 1mo ago First seen · 41 lines · 31 tokens per session scan A 7917b8eb0dca
impl-simplify is an agent published in the GitHub repository wei6bin/skills (2 stars, last pushed 11d ago), licensed MIT. It adds 62 tokens to every session and 904 once invoked, about $0.0002 per session on Opus 5.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.
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.
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.