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/sjarmak/coding-agent-workflows/simplifynpx skills add sjarmak/coding-agent-workflows --skill simplifygit clone --depth 1 https://github.com/sjarmak/coding-agent-workflowsWhat 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.00030 | $0.00405 |
| Opus 5 | $0.00015 | $0.00202 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 43 lines · 30 tokens per session scan A 113d58a7d8e8
simplify is a skill published in the GitHub repository sjarmak/coding-agent-workflows (2 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 405 once invoked, about $0.0002 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
browser-trace
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page…
planning-with-files
Manus-style persistent file-based planning for AI coding agents: keeps taskplan.md, findings.md, and progress.md on disk so work survives context loss and /clear. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring 5+ tool calls. Supports automatic session…
ai-elements
Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface.
exa-search
Use Exa MCP for current web, code/docs, company, people, and page-fetch research. Prefer current hosted tool schemas and note deprecated tools.
ontoly-software-graph
Use Ontoly's deterministic Software Graph and MCP capabilities for repository architecture, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source search.
product-decision-agent
中文产品决策 Agent。用于中国大陆互联网产品、运营、增长、商业化、数据、项目推进和组织协作场景：产品规划、需求分析、PRD、需求优先级、排期、版本规划、Roadmap、MVP、灰度、上线、迭代、增长停滞、拉新、投放、渠道、裂变、CAC、LTV、ROI、留存、转化、DAU/MAU、GMV、漏斗、社区运营、内容供给、创作者、用户运营、活动运营、私域、会员、定价、指标异常、数据口径、埋点、A/B…