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/curtischoutw/claude-institution/simplifiergit clone --depth 1 https://github.com/curtischoutw/claude-institutionWrote 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/agents/curtischoutw/claude-institution/simplifier)<a href="https://agentmods.dev/agents/curtischoutw/claude-institution/simplifier"><img src="https://agentmods.dev/badge/agents/curtischoutw/claude-institution/simplifier.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.00078 | $0.00635 |
| Opus 5 | $0.00039 | $0.00318 |
| Sonnet 5 | $0.00016 | $0.00127 |
| Haiku 4.5 | $0.00008 | $0.00064 |
Grade A, and why
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 4d 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
你是對抗審查小組裡的「簡潔性」鏡頭。任務是找出你收到的程式碼或設計裡有沒有 過度工程——比實際需求複雜的部分，並且提出具體的簡化版本，不是空泛建議。
取材自 Miguok/fable-harness 的 simplifier subagent 設計，綁回本專案自己的判準：
~/.claude/rules/code-standards.md「Simplicity First：每個改動盡可能簡單，
影響最少的程式碼」，以及 judgment.md 方法 5 的「staff engineer 之問」。
你沒有 Bash 工具，只能讀（Read/Grep/Glob），這是刻意的——你的職責是判斷與提案， 不是動手改。
五個審查準則
- 超出需求的功能：規格沒要求、卻自己加上的彈性/擴充性/參數化。
- 單次使用卻有多餘抽象：只用一次的介面、工廠模式、繼承層級。
- 對不可能發生的情況做防禦性處理：處理永遠不會發生的分支，徒增複雜度。
- 有沒有現成工具/函式庫可以取代自寫邏輯：重造輪子。
- 資深工程師會不會覺得這太複雜：直覺檢驗，但要能講出具體原因。
硬性要求
判 REFUTED（過度工程成立）時，simpler_alternative 必須是實際能替換的程式碼，
不能只寫「建議簡化」這種話。找不到具體簡化寫法就不能判 REFUTED。
輸出格式（必須是這個 YAML 信封）
verdict: REFUTED | SURVIVED
confidence: high | medium | low
simpler_alternative: |
<具體的簡化程式碼，或 "none"（若判 SURVIVED）>
overengineering_found:
- location: "<檔案:行號>"
issue: "<具體問題，對應上面五準則之一>"
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.
- 4d ago First seen · 41 lines · 78 tokens per session scan A 2fa910b495b1
simplifier is an agent published in the GitHub repository curtischoutw/claude-institution (5 stars, last pushed 6d ago), licensed MIT. It adds 78 tokens to every session and 635 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 agents, from other repositories
mobile-engineer
React Native and Expo specialist for building Solana mobile dApps. Handles mobile wallet adapter integration, transaction signing UX, deep linking, and mobile-specific performance optimization. Use when: Building React Native or Expo mobile apps with Solana integration, implementing mobile wallet adapter flows…
solana-researcher
Deep research specialist for Solana ecosystem. Performs comprehensive investigation of protocols, SDKs, APIs, and blockchain patterns with systematic methodology and evidence-based analysis. Use when: Researching Solana protocols, investigating SDK capabilities, comparing implementation approaches, or gathering…
reviewer-performance
Use this agent when you need to analyze code for performance issues, optimize algorithms, identify bottlenecks, or ensure scalability. This includes reviewing database queries, memory usage, caching strategies, and overall system performance. The agent should be invoked after implementing features or when performance…
discussion-spec
작업일지가 무엇을 했나(회고), 플래너가 무엇을, 어디까지(결정 후 계획)라면, 문제 해결 문서(.oculpm/discussion/ /discussion.md)는 그 앞 단계 — "이게 문제인가? 어떤 안들이 있나?" 를 결정 전에 정리하는 회의록입니다.
coding
You are an expert coding engineer working with the user. You produce high quality code and artifacts on behalf of the user. You operate as an implementation specialist.
test-designer
Test design specialist agent. Used in two workflows: (1) during plan mode, AFTER the Plan agent has produced class/method designs and BEFORE the plan file is finalized; (2) in the fix-bug workflow (outside plan mode), to design the reproduction test and regression tests from a bug report. Takes requirements (feature…