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 skills/evoelsewhere/evoflux/coding-simplificationnpx skills add evoelsewhere/evoflux --skill coding-simplificationgit clone --depth 1 https://github.com/evoelsewhere/evofluxWrote 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/evoelsewhere/evoflux/coding-simplification)<a href="https://agentmods.dev/skills/evoelsewhere/evoflux/coding-simplification"><img src="https://agentmods.dev/badge/skills/evoelsewhere/evoflux/coding-simplification.svg" alt="Measured on agentmods" 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 | $0.00078 | $0.00771 |
| Opus 5 | $0.00039 | $0.00385 |
| Sonnet 5 | $0.00016 | $0.00154 |
| Haiku 4.5 | $0.00008 | $0.00077 |
Grade A, and why
coding-simplification 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 today.
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplify existing code
Preserve behavior exactly; simplification is a clarity change, not a feature or a bug fix. Do not load bundled references when this skill activates.
Understand before changing
- State what the code currently does, including behavior that looks accidental — an existing edge case, ordering, or error path may be load-bearing even without a visible reason. Do not remove it without understanding why it is there (Chesterton's Fence): if the reason is unclear from code, tests, and history, name the uncertainty instead of deleting silently.
- Scope the change to what motivated it. Do not restyle unrelated code in the same file, rename unrelated symbols, or introduce an abstraction the current requirement does not need.
- Read references/simplification-signals.md for concrete shape-to-refactor mappings and the codemod threshold.
When the code's current callers or the reason a pattern exists is not evident
from the visible source, call code_context with action="search" once
using the behavior or literal in question. Skip search when the exact symbol
is already known.
For an exact symbol being simplified, use code_context to confirm direct
callers/references so the refactor's public shape is preserved for every
caller. Start at depth 1. Once the symbol and its callers are known, make the
graph the next structural observation instead of continuing broad discovery.
Keep refresh=true for the first indexed query and after edits. Use
refresh=false only for an immediate follow-up that intentionally reuses the
same index version.
Read references/code-context-contract.md only after a result exposes ambiguity, cross-repository scope, or another static fallback gap.
Simplify
Prefer clarity over cleverness and follow the file's existing conventions over a personally preferred style. Do not introduce a generic abstraction to replace a handful of concrete, similar lines; three similar lines are often clearer than a premature parameter or interface. For a refactor spanning more than roughly 500 lines, prefer a codemod/AST-based transform over manual edits so the change stays mechanical and reviewable.
What ships with it
4 files 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.
- today First seen · 76 lines · 78 tokens per session scan A acb7294f0e21
coding-simplification is a skill published in the GitHub repository evoelsewhere/evoflux (7 stars, last pushed today), licensed Apache-2.0. It adds 78 tokens to every session and 771 once invoked, about $0.0004 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-09-05.
Other skills, from other repositories
rove
Use when controlling Rove tasks, parallel coding attempts, hosted agent sessions, task lifecycle, or the daemon-owned issue tracker from a shell. Also the ONLY channel for messaging another agent session on this machine — rove api send, never a peer/MCP side channel.
E2E Testing Nori Skillsets Subcommands
Use when you need to interactively test a nori-skillsets CLI subcommand end-to-end via tmux, with full filesystem isolation.
general-video
The fallback workflow for authoring custom HyperFrames video compositions at any length or format — longer or multi-scene pieces, brand / sizzle reels, montages, title cards, static loops, and freeform compositions. Input- and length-agnostic. If a specialized workflow clearly fits the input — a marketed product, a…
release
Autonomously cut a Rove (@sma1lboy/rove) release end-to-end — detect the semver bump from pending changesets (flagging an upstream minor you didn't intend), run the release gates, bump/tag/push via scripts/release.sh, then poll the GitHub Actions Release workflow with gh until npm publish completes, diagnosing CI…
hyperframes-cli
HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, or remove-background, or when troubleshooting the…
changelog-generator
Draft Rove release notes as Changesets. Writes user-facing entries as .changeset/.md files for @sma1lboy/rove (consumed into packages/kobe/CHANGELOG.md at release time). Use when the user asks for "changelog", "release notes", "what changed", "add a changeset", or before cutting a version. Enforces Rove's no-soft-wrap…