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/olegvg/olegvg-skills/simplify-codenpx skills add olegvg/olegvg-skills --skill simplify-codegit clone --depth 1 https://github.com/olegvg/olegvg-skillsWrote 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/olegvg/olegvg-skills/simplify-code)<a href="https://agentmods.dev/skills/olegvg/olegvg-skills/simplify-code"><img src="https://agentmods.dev/badge/skills/olegvg/olegvg-skills/simplify-code.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.00081 | $0.00984 |
| Opus 5 | $0.00041 | $0.00492 |
| Sonnet 5 | $0.00016 | $0.00197 |
| Haiku 4.5 | $0.00008 | $0.00098 |
Grade A, and why
simplify-code 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 5d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
simplify-code — Behavior-Preserving Cleanup
Overview
Review changed code for concrete cleanup opportunities, then apply only fixes that preserve intended behavior. This is a portable version of Claude Code's /simplify workflow: reuse, simplification, efficiency, and altitude review before edits.
Input
- Optional target: current diff, file path, branch, PR, commit range, or pasted code.
- Project instructions that govern the changed files.
- Existing tests or verification commands, when discoverable.
Workflow
1. Establish Scope
Prefer the smallest review surface that matches the user's request.
- If the user passed a path, range, branch, PR, or pasted code, use that as scope.
- Otherwise review the current branch diff. Prefer
git diff @{upstream}...HEAD, fall back togit diff main...HEADorgit diff HEAD~1. - If there are uncommitted changes, or the range diff is empty, also include
git diff HEAD. - If the project is not git-backed, inspect the user-provided files or snippet.
- Read applicable project instructions for changed files before judging conventions or scope.
2. Review Four Cleanup Angles
Run the four angles independently. If the runtime supports subagents, run one pass per angle in parallel. If it does not, do four labeled passes yourself and keep findings separate until deduplication.
| Angle | Flag | Required evidence |
|---|---|---|
| Reuse | New code reimplements something already present in the codebase. | Name the existing helper, module, component, or pattern to reuse. |
| Simplification | Redundant or derivable state, copy-paste variants, deep nesting, dead code, needless abstraction, or tangled control flow. | Name the simpler form that preserves behavior. |
| Efficiency | Repeated computation, repeated I/O, independent work serialized, blocking work added to startup or hot paths, or long-lived closures capturing more scope than needed. | Name the cheaper alternative and the wasted work it removes. |
| Altitude | A fix is placed at the wrong depth, such as a brittle special case layered on shared infrastructure. | Name the underlying mechanism that should be generalized, or mark the improvement out of scope. |
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.
- 5d ago First seen · 88 lines · 81 tokens per session scan A d9844a13a811
simplify-code is a skill published in the GitHub repository olegvg/olegvg-skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 984 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-08-31.
Other skills, from other repositories
kapso-whatsapp
How to interact with Kapso WhatsApp from the swarm — read inbound webhook payloads (text AND media), fetch message history, send free-form messages within the 24h session window (and template messages outside it), mark-as-read, show the typing indicator, send reactions, download media, verify webhook signatures, and…
composio
Use Composio from Agent Swarm through the agent-swarm x composio CLI route, the swarmx MCP tool, or a registered ctx.api.composio script connection. Trigger when a task needs connected third-party app tools such as Gmail, Google Calendar, Google Docs, Google Drive, GitHub, Slack, Notion, or HubSpot through Tool Router…
attio-interaction
Generic Attio CRM REST API v2 recipes for querying records, upserting companies/people/deals, writing notes/tasks/comments, managing lists, and handling webhooks.
swarm-scripts
Bulk, repeat, fan-out, or data-heavy work: write and run swarm scripts (inline script-run, named script-upsert, durable launch-script-run). Covers the script-vs-tool rubric, the authoring contract (args first, ctx second), the seed catalog, connections and secrets, dbquery, and exposing a script as an API.
user-management
How to manage the user registry — creating users for new Slack/GitHub/GitLab/Linear identities, managing aliases, resolving users across platforms. Use when a new human interacts with the swarm or when user identity needs updating.
scheduled-task-resilience
Guardrails for polling, scheduled jobs, and long-running external operations. Use whenever a task waits on CI, builds, deploys, browser jobs, or another asynchronous API so work survives heartbeat checks without duplicate delivery.