Borrowing it
Nothing to install: this file belongs to victoriacity/openakari. 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/victoriacity/openakari/main/.claude/skills/simplify/SKILL.mdgit clone --depth 1 https://github.com/victoriacity/openakariWrote 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/victoriacity/openakari/simplify)<a href="https://agentmods.dev/skills/victoriacity/openakari/simplify"><img src="https://agentmods.dev/badge/skills/victoriacity/openakari/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/victoriacity/openakari/simplify"><img src="https://agentmods.dev/badge/skills/victoriacity/openakari/simplify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00018 | $0.00939 |
| Opus 5.5 | $0.00007 | $0.00376 |
| Sonnet 5.5 | $0.00004 | $0.00188 |
| Haiku 4.5 | $0.00002 | $0.00094 |
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 2mo 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/simplify
Review a plan, implementation, or design for unnecessary complexity. The argument is a file path (plan document, README, or source directory) or a description of the artifact. Read it first.
When to use this vs alternatives
- Use
/simplifywhen the primary concern is whether something is over-engineered — too many components, abstractions, or dependencies for the stated mission. - Use
/critiquewhen you want to find correctness problems (misattributions, grounding failures, provenance gaps). Critique asks "is this wrong?"; simplify asks "is this necessary?" - Use
/gravitywhen you suspect a pattern should be formalized (moved from manual to code/convention). Gravity adds structure; simplify removes it.
Core test
For every component, feature, abstraction, dependency, or configuration:
"If I removed this, would the stated mission fail?"
If the answer is no, it is a candidate for removal. The burden of proof is on inclusion, not exclusion.
Procedure
1. Identify the mission
Find the stated goal — the project's Mission/Done-when, the plan's objective, or the feature's purpose. If there is no stated mission, flag this as the first problem.
2. Inventory components
List every distinct component of the artifact:
- For a plan: each step, tool, dependency, page, feature
- For an implementation: each file, dependency, abstraction layer, configuration option
- For a design: each entity, relationship, interface, constraint
3. Apply removal tests
For each component:
Must-have test
Does the mission fail without this? Be strict — "nice to have" is not "must have." Common false must-haves:
- Error handling for impossible states
- Configuration for values that never change
- Abstractions over single implementations
- Features the user didn't ask for
- Documentation no one will read
- Tests for trivial logic (i.e., tests that duplicate what the type system already guarantees — NOT tests for simple runtime behavior, which the
/developskill requires per its TDD rule)
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.
- 2mo ago First seen · 114 lines · 18 tokens per session scan A 631e9beb7cad
simplify is a skill published in the GitHub repository victoriacity/openakari (47 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 939 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…