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 sjarmak/coding-agent-workflows --skill simplifygit clone --depth 1 https://github.com/sjarmak/coding-agent-workflowsWrote 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/sjarmak/coding-agent-workflows/simplify)<a href="https://agentmods.dev/skills/sjarmak/coding-agent-workflows/simplify"><img src="https://agentmods.dev/badge/skills/sjarmak/coding-agent-workflows/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/sjarmak/coding-agent-workflows/simplify"><img src="https://agentmods.dev/badge/skills/sjarmak/coding-agent-workflows/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.00030 | $0.00405 |
| Opus 5.5 | $0.00012 | $0.00162 |
| Sonnet 5.5 | $0.00006 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
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.
What it actually says
Simplify
Run after implementation, before review. Takes the current diff and proposes removals and consolidations that preserve behavior while cutting complexity.
When to activate
- Immediately after a feature or fix is implemented and tests pass.
- As step 4 of the
implement-reviewworkflow. - When a diff feels larger or more clever than the problem warrants.
What it looks for
- Dead paths: branches, params, or returns nothing reaches.
- Premature abstraction: interfaces/generics with a single caller; YAGNI.
- Over-engineering: configurability, indirection, or layering the task didn't ask for.
- Incidental churn: reformatting or renames unrelated to the change, which bloat review.
- Duplicated logic: only extract when the duplication is real (rule of three) and changes for the same reason.
How to apply
- Read the diff against its base ref.
- Propose concrete simplifications, each with a one-line rationale.
- Apply accepted ones and commit them separately so they're visible as simplification in review, not mixed into the feature commit.
- For anything you choose not to simplify, say why (sometimes the verbose form is clearer; note it so review doesn't re-litigate).
In Claude Code this delegates to the code-simplifier subagent. In a
single-agent runtime (Codex/Amp), perform the same pass inline.
Boundary
Simplify never changes behavior. If a "simplification" would alter what the code does, that's a design change; route it back through planning, not through here.
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 · 43 lines · 30 tokens per session scan A 113d58a7d8e8
simplify is a skill published in the GitHub repository sjarmak/coding-agent-workflows (6 stars, last pushed 17d ago), licensed MIT. It adds 30 tokens to every session and 405 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-31.
Other skills, from other repositories
Agent Instruction Drift Check
Procedure for comparing an agent-facing instruction doc (AGENTS.md/CLAUDE.md-style) against the actual current code and configuration to find and flag mismatches.
karpathy-guidelines
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
improve-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
agent-watchdog
Use when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log, or pasted run summary. Monitor until the other agent is done or blocked, reconstruct what the user asked, independently investigate the same…
find-simplifications
Use when asked to find or plan Cherry Studio cleanup, simplification, refactoring, dead-code removal, duplicated state removal, unnecessary APIs, speculative generality, or library replacements, especially when the result should become evidence-backed proposed Agent Notes.
no-comments
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.