Borrowing it
Nothing to install: this file belongs to DeL-TaiseiOzaki/claude-code-orchestra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DeL-TaiseiOzaki/claude-code-orchestra/main/.claude/skills/simplify/SKILL.mdgit clone --depth 1 https://github.com/DeL-TaiseiOzaki/claude-code-orchestraWrote 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/del-taiseiozaki/claude-code-orchestra/simplify)<a href="https://agentmods.dev/skills/del-taiseiozaki/claude-code-orchestra/simplify"><img src="https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/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/del-taiseiozaki/claude-code-orchestra/simplify"><img src="https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/simplify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 96 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00016 | $0.01947 |
| Opus 5 | $0.00008 | $0.00974 |
| Sonnet 5 | $0.00003 | $0.00389 |
| Haiku 4.5 | $0.00002 | $0.00195 |
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 3d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplify Code
Simplify and refactor $ARGUMENTS.
This skill edits source code while promising not to change behaviour and not to widen its own scope. Both promises are checked rather than asserted: Step 0 records a gate baseline and the declared target set, and Step 5 compares against it. A refactor whose baseline was never recorded cannot be reported as verified.
Declared Scope
Resolve $ARGUMENTS into a concrete list of files and/or directories before
editing anything, and pass each one as a --scope entry in Step 0. That list
is the answer to "was this a refactor or a rewrite" — anything else that changes
is reported as out_of_scope_files and fails Step 5.
Simplification Principles
- Single Responsibility - 1 function = 1 thing
- Short Functions - Target under 20 lines
- Shallow Nesting - Early return, depth ≤ 2
- Clear Naming - Clear enough to not need comments
- Type Hints Required - On all functions
Steps
0. Record the Baseline (mandatory, before any edit)
python3 .claude/skills/simplify/simplify_gate.py --phase before \
--scope {target file or dir} [--scope {another}] [--base main]
It runs _shared/verify.sh and _shared/gather_diff.py and writes
.claude/logs/simplify-baseline.json: the gate status of every tool as it is
now, the current HEAD, the declared scope, and any file that was already
modified before you started. Without this, a gate that was red the whole time is
indistinguishable from a regression this refactor introduced.
Read the JSON:
overall_before—pass/fail/no_gates. Onfail, note which tools are in the baseline as failing; Step 5 will report them aspre_existing_failuresrather than blaming your refactor.pre_existing_changes[]— dirty files you did not touch, excluded from the scope check later.baseline_file,artifacts[].
Exit codes: 0 baseline recorded · 1 bad arguments, or --scope missing —
without a declared target set "no scope creep" cannot be checked · 2 no gate
could run at all, so the refactor would be unverifiable · 3 verify.sh /
gather_diff.py failed, or the baseline could not be written.
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.
- 3d ago Changed 73aa5f032517
- 9d ago First seen · 211 lines · 16 tokens per session scan A 6c06af407f2c
simplify is a skill published in the GitHub repository DeL-TaiseiOzaki/claude-code-orchestra (194 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 1,947 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…