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/awish021/opencode/simplify-codenpx skills add Awish021/opencode --skill simplify-codegit clone --depth 1 https://github.com/Awish021/opencodeWhat 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.00015 | $0.00317 |
| Opus 5 | $0.00008 | $0.00159 |
| Sonnet 5 | $0.00003 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
simplify-code 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.
What it actually says
Simplify Code
What I do
I simplify recently modified code to improve clarity, consistency, and maintainability without changing behavior.
When to use this
Use this skill proactively after code is written or modified, unless the user asks for a different scope.
Principles
- Preserve behavior exactly. Do not change outputs, side effects, or external contracts.
- Favor clarity over brevity. Explicit, readable code is preferred to compact or clever code.
- Reduce complexity. Simplify control flow, reduce nesting, and remove redundant logic.
- Keep scope focused. Only touch recently modified code unless the user explicitly asks for broader refactoring.
- Respect project conventions. Follow existing naming, formatting, and structural patterns.
Guardrails
- Do not change public APIs or documented behavior.
- Do not alter performance characteristics unless explicitly requested.
- Avoid micro-optimizations that reduce readability.
- Avoid clever tricks, dense one-liners, or nested ternaries.
- Do not remove useful abstractions that improve organization.
- Do not add comments unless they clarify a non-obvious block.
Process
- Identify recently modified sections.
- Look for unnecessary complexity or duplication.
- Simplify with clear names and straightforward structure.
- Verify behavior is unchanged.
- Document only meaningful changes that affect understanding.
Output expectations
- Cleaner, more readable code with the same functionality.
- Minimal, targeted edits focused on the modified areas.
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 · 45 lines · 15 tokens per session scan A 01efecf2177c
simplify-code is a skill published in the GitHub repository Awish021/opencode (11 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 317 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…