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 skills add znlgis/my-opencode-deepseek-config --skill simplifygit clone --depth 1 https://github.com/znlgis/my-opencode-deepseek-configWrote 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/znlgis/my-opencode-deepseek-config/simplify)<a href="https://agentmods.dev/skills/znlgis/my-opencode-deepseek-config/simplify"><img src="https://agentmods.dev/badge/skills/znlgis/my-opencode-deepseek-config/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/skills/znlgis/my-opencode-deepseek-config/simplify"><img src="https://agentmods.dev/badge/skills/znlgis/my-opencode-deepseek-config/simplify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00070 | $0.01078 |
| Opus 5.5 | $0.00028 | $0.00431 |
| Sonnet 5.5 | $0.00014 | $0.00216 |
| Haiku 4.5 | $0.00007 | $0.00108 |
Grade A, and why
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 1mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplify
Improve code readability and reduce cognitive load without altering behavior.
For deleting code that is verified-unreferenced (not simplifying it), use the
remove-deadcode skill.
Core rule
The code must do exactly the same thing after simplification. No behavior changes, no "while I'm here" improvements, no API surface modifications. If a test breaks after simplification, the simplification was wrong — revert it.
When to use me
- Code is "too clever" — over-abstracted, deeply nested, hard to follow
- After a feature lands and code has accumulated cruft
- Review feedback says "this is hard to understand"
- You spot unnecessary indirection: wrappers that don't add value, interfaces with only one implementation, functions called exactly once
Simplification checklist
Apply each pattern only if it reduces complexity without changing behavior:
Reduce nesting
- Early returns — replace
if (x) { ... entire function ... }withif (!x) return. Flattens 3+ levels of nesting into a straight line. - Guard clauses — check preconditions at the top and bail early.
- Extract deeply nested blocks into well-named functions only when the extraction clarifies intent (not reflexively).
Remove unnecessary abstraction
- Single-caller functions — inline them. A function called from exactly one place is just an indirection tax.
- Single-implementation interfaces — remove the interface and use the concrete type directly.
- Thin wrappers — if a function just calls another function with the same arguments plus one default, ask: is this wrapper pulling its weight?
- Overly generic utilities — a
createMapWithDefaultValue(key, defaultVal, strategy, cachePolicy)called only ascreateMapWithDefaultValue(x, {}, 'lru', 'none')should just be the concrete code.
Reduce variable count
- Inline single-use variables — if a variable is used exactly once, inline its value at the use site. This is the single highest-leverage simplification.
- Eliminate temporary "explanation" variables — if the variable name just
restates what the RHS already says, delete it.
- Bad:
const isActive = user.status === 'active'; if (isActive) ... - Better:
if (user.status === 'active') ...(the condition is self-documenting)
- Bad:
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.
- 1mo ago Changed · +2 lines dfa72c26615e
- 1mo ago Changed · +3 tokens per session 8e75682f61a3
- 1mo ago First seen · 109 lines · 67 tokens per session scan A faed67d2603e
simplify is a skill published in the GitHub repository znlgis/my-opencode-deepseek-config (59 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 1,078 once invoked, about $0.0003 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-30.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
archify-review
Review Archify issues, PRs, or code through value, cost, and impact to support evidence-based maintenance decisions. Use for issue triage, change reviews, and code quality assessments.
code-review
Run a final code review on a pull request.
code-breaking-changes
Search for breaking changes in external integration surfaces.
plannotator
Reference for using Plannotator (its plannotator tool when you have one, otherwise the CLI): plan review, code review, annotating files, URLs, folders, and running local apps, annotating the last assistant message, browsing archived plan decisions, exporting or sharing Guided Reviews, and the Plannotator Inbox…
gh-pr-review
Automated Cherry Studio review for local branches, PRs, commits, files, architecture docs, and repository skills. Use for code or documentation reviews that need project-specific naming, main/renderer/shared placement and dependency rules, IpcApi and DataApi boundaries, lifecycle/service ownership, renderer hooks…