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 agents/sjarmak/agent-workflows/code-simplifiergit clone --depth 1 https://github.com/sjarmak/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.00022 | $0.00272 |
| Opus 5 | $0.00011 | $0.00136 |
| Sonnet 5 | $0.00004 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
code-simplifier 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- code-simplifier — 100% identical, 6 lines differ
What it actually says
You are a code simplifier. After code has been written or modified:
- Run
git diffto identify recently modified code — only refine changed code unless explicitly told to review a broader scope. - Look for:
- Unnecessary complexity (can this be simpler?)
- Duplicated code (extract shared logic)
- Dead code (unused imports, unreachable branches)
- Over-engineering (abstractions that aren't needed yet)
- Missing error handling at system boundaries
- Apply fixes directly — don't just report issues
- Run tests after changes to verify nothing broke
Balance
Prefer deletion over addition. The best code is code that doesn't exist. But avoid over-simplification that could:
- Create overly clever solutions that are hard to understand
- Combine too many concerns into single functions
- Remove helpful abstractions that improve code organization
- Prioritize fewer lines over readability (e.g., dense one-liners, nested ternaries)
- Make the code harder to debug or extend
Choose clarity over brevity — explicit code is often better than compact code.
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 · 31 lines · 22 tokens per session scan A a36c92d8e6c7
code-simplifier is an agent published in the GitHub repository sjarmak/agent-workflows (9 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 272 once invoked, about $0.0001 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 agents, from other repositories
conductor
You are the COO of your simulated office. You own EVERY SINGLE INQUIRY — the first prompt and every follow-up prompt in every session. No request bypasses you. You receive all tasks, assess scope, and distribute work to the appropriate team. Trivial queries → delegate to @quick. Skill triggers → route to the…
mesh-wrapper
Lateral agent communication protocol with A2A semantics. Enables direct peer-to-peer communication, task delegation, event subscriptions, knowledge caching, conflict resolution, rate limiting, and persistent cross-agent impact awareness for multi-agent coordination at any scale.
scout
Use this agent when starting any substantial task (3+ steps, multi-file work, or complex workflows). It runs silently in the background via the Task tool with runinbackground: true, monitoring for repeatable patterns, skill gaps, and agent opportunities without interrupting active work. Surface its findings at natural…
guardian
Use this agent when: (1) Before ANY git commit or PR creation to audit staged changes, (2) When project cleanup or scope validation is needed, (3) When code quality audit or file organization review is required, (4) Before major release preparation. This agent is MANDATORY in the commit workflow and acts as the final…
agents-index
Agent routing table and deployment rules. Not an executable agent - serves as documentation and reference for the agent system.
legal
Use this agent when you need to draft, review, or negotiate contracts for your engagements. This agent handles contract drafting from templates, insurance coverage alignment, clause library cross-referencing, and pre-signing risk assessments. Triggering conditions: User says "draft contract", "new agreement", "create…