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 commands/ishandutta2007/awesome-agent-skills/code-simplifygit clone --depth 1 https://github.com/ishandutta2007/Awesome-Agent-SkillsWhat 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.00014 | $0.00220 |
| Opus 5 | $0.00007 | $0.00110 |
| Sonnet 5 | $0.00003 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
code-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 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.
This is a copy
100% identical to code-simplify — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Invoke the agent-skills:code-simplification skill.
Simplify recently changed code (or the specified scope) while preserving exact behavior:
- Read CLAUDE.md and study project conventions
- Identify the target code — recent changes unless a broader scope is specified
- Understand the code's purpose, callers, edge cases, and test coverage before touching it
- Scan for simplification opportunities:
- Deep nesting → guard clauses or extracted helpers
- Long functions → split by responsibility
- Nested ternaries → if/else or switch
- Generic names → descriptive names
- Duplicated logic → shared functions
- Dead code → remove after confirming
- Apply each simplification incrementally — run tests after each change
- Verify all tests pass, the build succeeds, and the diff is clean
If tests fail after a simplification, revert that change and reconsider. Use code-review-and-quality to review the result.
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 · 23 lines · 14 tokens per session scan A 71e9e8d38c5c
code-simplify is a command published in the GitHub repository ishandutta2007/Awesome-Agent-Skills (20 stars, last pushed 22d ago), licensed MIT. It adds 14 tokens to every session and 220 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-simplify, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
screen-usecase
筛选、验证并撰写 OpenClaw 用例。输入来源 URL 或描述，输出适配评估或完整用例 PR。.
code-review
Code review — local uncommitted changes or GitHub PR (pass PR number/URL for PR mode).
docs-fe
Generate a concise FE handoff doc for changed endpoints — branch, APIs, request/response contracts, search params, error codes.
coding-level
Set Claude's coding explanation level for this session/project (-1=Default → 5=God Mode).
brainstorm
Explore and debate solutions before writing code — scout codebase, ask clarifying questions, research options, and produce a structured decision report. Ends with → /ck:plan (implement) or /ck:journal (archive). No code is written.
cook
Implement a plan phase by phase. Cook never writes or runs tests; every phase requires an APPROVED ck:quality gate before completion. Modes: --fast or --hard. Flag: --tdd. --json selects the phased master plan.json; --plan selects a Markdown plan.md.