Borrowing it
Nothing to install: this file belongs to xsovad06/sova. 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/xsovad06/sova/main/.agents/skills/sova-simplify/SKILL.mdgit clone --depth 1 https://github.com/xsovad06/sovaWrote 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/xsovad06/sova/sova-simplify)<a href="https://agentmods.dev/skills/xsovad06/sova/sova-simplify"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/sova-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/xsovad06/sova/sova-simplify"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/sova-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.00023 | $0.00650 |
| Opus 5.5 | $0.00009 | $0.00260 |
| Sonnet 5.5 | $0.00005 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
sova-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 9d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplify
Review all changed code for opportunities to reduce complexity, eliminate duplication, and improve quality.
Scope: the arguments provided when this skill is invoked
Instructions
Step 1: Get the Diff Scope
Compare against the fork point with the remote base (three dots), not a local main: two dots against a stale or moved base also lists the base's own newer commits as if this branch made them.
BASE=$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's#^origin/##')
BASE=${BASE:-main}
git fetch --quiet origin "$BASE"
git diff "origin/$BASE"...HEAD --stat
git diff --cached --stat
git diff --stat
Step 2: Review Each Changed File
For each changed file, read the entire file and check:
- Code reuse: does new code duplicate existing utilities or helpers? Search the codebase for similar patterns.
- Over-engineering: unnecessary abstractions, premature generalization, excessive configurability for one-time operations.
- Dead code: unused imports, unreachable branches, commented-out code.
- Redundancy: repeated logic that could be a shared helper (only if 3+ occurrences).
- Complexity: can any function be simplified without losing clarity?
- Efficiency: redundant computations, repeated file reads, duplicate API calls.
- Naming: unclear variable or function names that could be more descriptive.
Step 3: Apply Simplifications
Apply each simplification directly. After changes, verify tests still pass, skipping only when an identical check already passed earlier in this autonomous pipeline cycle for this exact worktree state (a no-op outside the autonomous pipeline: sova checks should-skip only ever reports a skip there). Here that can only happen when no simplification was applied, since any edit changes the state the skip is keyed to:
if sova checks should-skip "make check"; then
echo "Full check already passed for this worktree state earlier in the pipeline cycle; skipping re-run."
else
make check && { sova checks record "make check" --passed || true; }
fi
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.
- 9d ago Changed · +4 lines 2d2ca8088295
- 14d ago Changed · +5 lines d46b85ccf1e1
- 16d ago Changed 16e8734ff18f
- 22d ago First seen · 67 lines · 23 tokens per session scan A e7f47dd447a7
sova-simplify is a skill published in the GitHub repository xsovad06/sova (2 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 650 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-10-08.
Other skills, from other repositories
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
code-review
You are a senior code reviewer. You receive diffs via stdin.
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…
audit-ci
Run and analyze Elements cold CI performance profiles and propose evidence-backed build, test, lint, and dependency-graph improvements. Use whenever asked to profile or benchmark pnpm run ci, rerun ci:profile, create a CI performance audit, compare CI timings, find bottlenecks or the completion path, investigate a CI…
review
Adversarial review of an increment before it ships, by a fresh context or another model family; every finding cites path:line and is re-verified. Use for "review", "qa", "critique this".
tech-debt-ci-review
Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.