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 ils15/pantheon-legacy --skill simplifygit clone --depth 1 https://github.com/ils15/pantheon-legacyWrote 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/ils15/pantheon-legacy/simplify)<a href="https://agentmods.dev/skills/ils15/pantheon-legacy/simplify"><img src="https://agentmods.dev/badge/skills/ils15/pantheon-legacy/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/ils15/pantheon-legacy/simplify"><img src="https://agentmods.dev/badge/skills/ils15/pantheon-legacy/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.00023 | $0.02414 |
| Opus 5.5 | $0.00009 | $0.00966 |
| Sonnet 5.5 | $0.00005 | $0.00483 |
| Haiku 4.5 | $0.00002 | $0.00241 |
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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplify Skill
Behavior-preserving code simplification. Reduce complexity, eliminate noise, and improve readability without changing what the code does.
When to load this skill
Load when asked to:
- "Simplify this function/module"
- "Reduce complexity without changing behavior"
- "Clean up this code"
- "Refactor for readability"
- "Remove dead code / unused paths"
Core Rule: Behavior Is Invariant
Every simplification MUST preserve observable behavior:
- Same inputs → same outputs
- Same side effects
- Same error conditions
- Same public API surface
If a simplification changes behavior, it is a bug, not a simplification.
Simplification Checklist
Work through these categories in order. Stop at any category where a change risks behavior — flag it and ask before proceeding.
1. Dead Code Removal (zero-risk)
- Remove imports that are never used
- Remove variables assigned but never read
- Remove functions/methods never called (verify with usages search)
- Remove commented-out code blocks older than the last commit
- Remove
passstatements in non-empty bodies
Verification: Run existing tests. If they pass, the removal was safe.
2. Redundancy Elimination (low-risk)
- Replace repeated literals with a named constant
- Collapse duplicate conditional branches with identical bodies
- Merge nested
ifchains into a single compound condition where intent is clearer - Remove double negations (
not not x→bool(x)or justxwhere truthy is enough) - Replace
if x == True:withif x:andif x == False:withif not x:
3. Standard Library Substitution (medium-risk — test after each)
- Replace manual loop patterns with built-ins (
any(),all(),sum(),min(),max()) - Replace
dict.get(key, None)withdict.get(key)(same default) - Replace string concatenation in loops with
"".join() - Replace manual null-checks on dict access with
dict.get() - Replace
len(x) == 0withnot x(only for types where falsy = empty)
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 First seen · 311 lines · 23 tokens per session scan A afe69a8adb3f
simplify is a skill published in the GitHub repository ils15/pantheon-legacy (12 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 2,414 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
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"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…