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 skills/dcspirit-23/dsh-inspired-code-simplification-skill/find-code-simplificationsnpx skills add DCspirit-23/DSH-inspired-Code-Simplification-Skill --skill find-code-simplificationsgit clone --depth 1 https://github.com/DCspirit-23/DSH-inspired-Code-Simplification-SkillWrote 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/skills/dcspirit-23/dsh-inspired-code-simplification-skill/find-code-simplifications)<a href="https://agentmods.dev/skills/dcspirit-23/dsh-inspired-code-simplification-skill/find-code-simplifications"><img src="https://agentmods.dev/badge/skills/dcspirit-23/dsh-inspired-code-simplification-skill/find-code-simplifications.svg" alt="Measured on agentmods" 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 | $0.00072 | $0.01509 |
| Opus 5 | $0.00036 | $0.00754 |
| Sonnet 5 | $0.00014 | $0.00302 |
| Haiku 4.5 | $0.00007 | $0.00151 |
Grade A, and why
find-code-simplifications 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 5d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Code Simplifications
Find a few meaningful simplifications with strong evidence. Follow the code and its contracts, keep judgment active, and prefer net reductions in concepts and maintained surface area over cosmetic line-count wins.
Establish The Investigation
- Determine the requested scope: a branch or PR diff, named modules, or the whole repository.
- For branch work, establish a fixed comparison base from the user's target, PR metadata, or the verified merge base. Include staged, unstaged, and relevant untracked work when the request covers the current working tree.
- Read the repository instructions and the architecture, testing, dependency, compatibility, and design-decision documents that govern the selected scope.
- Inspect the working tree before proceeding and preserve unrelated user changes.
- Begin read-only. Produce findings first; edit code only when the user explicitly asks for implementation.
Complete this stage when the scope, comparison point, applicable rules, and mutation boundary are explicit.
Identify Strong Candidates
Look for simplifications where the current design costs more than it buys:
- A public method, event, configuration option, helper, package, registry entry, or test artifact has no production consumer.
- Tests or documentation are the only consumers, and the behavior they preserve is not load-bearing.
- Multiple representations, caches, flags, or events mirror the same fact.
- An interface or abstraction forces implementations to support capabilities no production caller uses.
- A wrapper, package, layer, or registry adds indirection without owning policy, state, translation, or lifecycle.
- A feature carries speculative generality for scenarios with no current product or platform owner.
- An invariant, rollback path, expected-output corpus, or special-case test exists only to protect an unused surface.
- Code added and later removed left compatibility branches, configuration, migrations, documentation, snapshots, or tests behind.
- Hand-rolled infrastructure duplicates a standard-library feature or a well-maintained dependency and replacement would produce a real net deletion.
- Similar branches, adapters, commands, or data transformations can share one source of truth without hiding meaningful differences.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 104 lines · 72 tokens per session scan A c2c01d88b149
find-code-simplifications is a skill published in the GitHub repository DCspirit-23/DSH-inspired-Code-Simplification-Skill (28 stars, last pushed 18d ago), licensed MIT. It adds 72 tokens to every session and 1,509 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…