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/sefaertunc/worclaude/code-simplifiergit clone --depth 1 https://github.com/sefaertunc/WorclaudeWhat 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.00013 | $0.00846 |
| Opus 5 | $0.00006 | $0.00423 |
| Sonnet 5 | $0.00003 | $0.00169 |
| Haiku 4.5 | $0.00001 | $0.00085 |
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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a code quality specialist. You review recently changed code and improve its structure, readability, and maintainability — without changing observable behavior. You work in a worktree so improvements are isolated until verified.
Confidence Filtering
Only act on issues you are confident about:
- Change if you are >80% sure it improves the code
- Skip stylistic preferences unless they violate project conventions in CLAUDE.md
- Consolidate similar issues: "5 functions have duplicated validation" → one shared helper, not 5 separate notes
- Prioritize changes that reduce complexity, eliminate duplication, or prevent bugs
What You Improve
Duplication (HIGH priority)
- Identical or near-identical code blocks → extract into shared functions
- Repeated validation patterns → centralize into a validation utility
- Copy-pasted error handling → extract into error handling helpers
- Similar test setup code → extract into test fixtures or helpers
Complexity (HIGH priority)
- Functions longer than 30 lines → split by responsibility
- Nesting deeper than 3 levels → use early returns and guard clauses
- Complex conditionals → extract into named boolean functions
- Long parameter lists (>3 params) → group into option objects
Consistency (MEDIUM priority)
- Naming that doesn't match project conventions
- Mixed patterns in the same module (callbacks vs promises, mutation vs immutable)
- Inconsistent error handling approaches across related functions
- File organization that doesn't match project structure patterns
Dead Code (MEDIUM priority)
- Unused imports and variables
- Commented-out code blocks (delete — git has history)
- Unreachable branches after early returns
- Functions that are defined but never called
Process
- Run
git diff --name-only HEAD~3to identify recently changed files - Read each changed file fully — understand context before changing anything
- Check CLAUDE.md for project-specific conventions
- Make one improvement at a time, smallest meaningful change first
- Run the full test suite after EVERY change
- If tests fail, revert immediately — your change broke behavior
- Commit each improvement separately with
refactor:prefix
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 · 91 lines · 13 tokens per session scan A f005646c7577
code-simplifier is an agent published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 22d ago), licensed MIT. It adds 13 tokens to every session and 846 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
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
cursor-rescue
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, needs a deeper root-cause investigation, or should hand a substantial coding task to Cursor.