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/vignesh2027/ai-agent-skills/code-simplificationnpx skills add vignesh2027/AI-AGENT-SKILLS --skill code-simplificationgit clone --depth 1 https://github.com/vignesh2027/AI-AGENT-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/skills/vignesh2027/ai-agent-skills/code-simplification)<a href="https://agentmods.dev/skills/vignesh2027/ai-agent-skills/code-simplification"><img src="https://agentmods.dev/badge/skills/vignesh2027/ai-agent-skills/code-simplification.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.00017 | $0.00613 |
| Opus 5 | $0.00009 | $0.00307 |
| Sonnet 5 | $0.00003 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
code-simplification 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 4d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Every line of code is a liability. Complexity that serves no purpose makes systems harder to understand, harder to test, and harder to change. This skill removes accidental complexity while preserving intentional complexity and essential behavior.
When to Use
- When a PR review reveals unnecessarily complex code
- When a function is hard to test because it does too many things
- When adding a feature to existing code requires understanding too much context
- As part of the
/simplifyworkflow
Process
Step 1: Understand before you remove (Chesterton's Fence)
Before removing any code that seems unnecessary: understand why it was written. If you don't know why a fence exists, don't remove it. Find out first.
Step 2: Identify the complexity types
- Accidental complexity: complexity from poor implementation choices
- Essential complexity: complexity inherent to the problem domain
Only remove accidental complexity. Essential complexity cannot be removed — only managed.
Step 3: Look for these simplification opportunities
Dead code: Code that is never executed. Remove it (git remembers it).
Premature abstraction: Abstractions that are more complex than the thing they abstract. Inline them.
Unnecessary indirection: Function A calls function B which calls function C and each is 5 lines. Collapse them.
Redundant comments: Comments that say what the code already says. Delete them. Keep comments that explain WHY.
Magic numbers: Replace if (retries > 3) with if (retries > MAX_RETRIES).
Over-engineered error handling: 10 levels of nested try/catch for a case that can't happen. Simplify.
Duplicate logic: The same logic in 3 places. Extract to one place.
Step 4: Simplify in small steps
One simplification at a time. Run tests after each step.
Step 5: Verify behavior is unchanged
The test suite must pass. If there are no tests, write tests for the behavior you're simplifying before you simplify it.
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.
- 4d ago First seen · 69 lines · 17 tokens per session scan A 8802d35e9706
code-simplification is a skill published in the GitHub repository vignesh2027/AI-AGENT-SKILLS (2 stars, last pushed 6d ago), licensed MIT. It adds 17 tokens to every session and 613 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 skills, from other repositories
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
agy-delegate
Delegate a coding task to the Google Antigravity CLI (agy) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use…
mcp-scripting
Write mcpScript JavaScript for discovering, inspecting, and calling MCP tools.
subagent-driven-development
Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.