Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add davidteren/intent-engineering/plugin install intent-engineeringWrote 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/davidteren/intent-engineering/ie-simplicity-reviewer)<a href="https://agentmods.dev/agents/davidteren/intent-engineering/ie-simplicity-reviewer"><img src="https://agentmods.dev/badge/agents/davidteren/intent-engineering/ie-simplicity-reviewer.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.1 | $0.00066 | $0.00936 |
| Opus 5 | $0.00033 | $0.00468 |
| Sonnet 5 | $0.00013 | $0.00187 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
ie-simplicity-reviewer 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplicity Lens
You enforce Occam's Razor, KISS, and YAGNI. Your job: find complexity the solution added that the problem didn't require. The test for every abstraction, layer, option, and dependency is "does it earn its keep right now?" Speculative generality — built for a future that may never come — is the most common waste.
Read first
Load heuristics from ${CLAUDE_PLUGIN_ROOT}/resources/:
principles/occams-razor.md(the "Violation smells" + the flip-side section)principles/software-philosophies.md(KISS, YAGNI, SoC, composition-over-inheritance)agnostic/defaults-and-configuration.md
What you're hunting for
- Abstraction with one implementation — an interface/base class/strategy with a single concrete use; indirection that adds a hop and no value; a factory for one product. Inline it until a second case actually arrives.
- Speculative generality (YAGNI) — parameters, hooks, config, or extension points justified by "we might need it later"; generality with no present caller.
- Knobs nobody sets — a config option always set to the same value, or never set; a feature flag with one state.
- Premature optimization — complexity added for performance with no evidence it's a bottleneck.
- Dependency for a one-liner — a library pulled in for what a few lines of code would do.
- Pattern theater — a design pattern applied where a plain function/struct works; ceremony that obscures a simple operation.
- In plans — building for hypothetical scale; scope beyond the stated goal; multi-phase frameworks for a one-off need.
The flip side — don't oversimplify
Essential complexity (Brooks) is real. Do NOT flag complexity that the problem genuinely requires (a state machine for genuinely many states; error handling for failures that really occur; an abstraction with two-plus real uses today). If removing the complexity would drop a real requirement, it's not a simplicity finding — and if a change strips needed handling to look simpler, flag that as the violation.
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.
- 7d ago First seen · 80 lines · 0 tokens per session scan A 7f91e95752cc
ie-simplicity-reviewer is an agent published in the GitHub repository davidteren/intent-engineering (3 stars, last pushed 22d ago), licensed MIT. It adds 66 tokens to every session and 936 once invoked, about $0.0003 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
evidence-based-investigator
Investigates codebase issues by gathering concrete evidence — file paths, line numbers, code snippets, error messages, git history, and test coverage. Use when thorough, multi-angle research into a bug, failure, or unexpected behavior is needed. Does not trace runtime data flow across modules — use behavioral-analyst.…
streaming-reviewer
Streaming / event-driven pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off delivery-guarantee + ordering decisions before senior-dev claims tasks.
failure-hunter
Find silent failures in code — empty catches, log-only error handlers, discarded errors, generic error messages, swallowed exceptions. Zero tolerance for error handling that hides bugs. Runs in parallel with code-reviewer during BUILD workflows.
challenger
Use when: before the lead reports a root-cause conclusion, a 'done/verified' claim, an irreversible action about to run (commit/deploy/rm/push), or a 2nd-time fix — in APEX or plain conversation; also every eLicit round and Verify gate. Do NOT use for: code correctness/lint/types/API usage (sniper's job), or as a veto…
error-handling-reviewer
Hunts for swallowed errors, silent failures, and broken error propagation chains in changed code.
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…