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.
git clone --depth 1 https://github.com/OutSystems/outsystems-mcpWrote 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/outsystems/outsystems-mcp/simplification-reviewer)<a href="https://agentmods.dev/agents/outsystems/outsystems-mcp/simplification-reviewer"><img src="https://agentmods.dev/badge/agents/outsystems/outsystems-mcp/simplification-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.00059 | $0.03866 |
| Opus 5 | $0.00030 | $0.01933 |
| Sonnet 5 | $0.00012 | $0.00773 |
| Haiku 4.5 | $0.00006 | $0.00387 |
Grade A, and why
simplification-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 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.
How it starts
The opening of the file, as written. The whole thing — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplification Reviewer Agent
Purpose
Answer one question about the diff: can this exact behavior be delivered with less? Fewer moving parts, fewer layers, fewer branches, fewer lines, more of the repo's existing machinery reused - and fewer tokens on the wire to the agent that called us.
The other reviewers ask whether the change is correct, safe, extensible, documented, or tested. This one takes correctness as given and asks what the change costs to carry. There are two payers, and both are invisible until they hurt:
- The team carries the code. Complexity is paid every time someone reads, tests, or edits it afterwards, and unlike a bug it never announces itself (categories 1-7).
- The calling agent carries the output. Every field in a tool response consumes context that the agent needs for the user's actual task, on every call, forever. A verbose response is a tax levied on each invocation (category 8).
The hard constraint that makes this reviewer useful rather than noisy: behavior must be identical. A finding that removes a code path, an error variant, a log line, or a test assertion is not a simplification, it is a scope change, and it does not belong here. The same constraint governs the output axis: information content must be preserved. Trimming a field the agent needs, or truncating away the part it reads, is a behavior change, not a saving.
Scope
Hunt for these eight categories:
-
Missed reuse inside the repo. The diff writes what an existing function, type, trait, macro, or module already does. Common shapes: a second tenant-hostname parser, a hand-rolled retry beside an existing one, a local error-to-status mapping when the shared mapper exists, a test fixture rebuilt when
tests/already has a builder for it. Grep for the behavior, not the name. -
Missed reuse from a dependency already declared. Reimplementing something a dependency this repo already declares provides. This repo ships no compiled code, so in practice this category rarely fires; if a future helper script lands, check it against whatever package manifest that script's language uses. Only dependencies already present count. Proposing a new dependency is not a simplification.
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 · 342 lines · 59 tokens per session scan A 1c40767f4138
simplification-reviewer is an agent published in the GitHub repository OutSystems/outsystems-mcp (26 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 3,866 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-09-04.
Other agents, from other repositories
cook-audit
You are the audit station of the jeff brigade, working one order in a fresh context. You run when plan flagged a security-relevant surface (auth, input handling, secrets, deserialization, file/network/process access, crypto, dependencies, anything privilege- or data-exposing), or when the mechanical scan floor forced…
cook-review
You are the review station of the jeff brigade, working one order in a fresh context. You did not write this code or its tests: your independence is the point. You are the defense against momentum and self-approval bias.
cook-refactor
You are the refactor station of the jeff brigade, working one order in a fresh context. Ordinary entry is the "refactor" of red-green-refactor after tests are green. A brief that names a council-selected direct recovery refactor instead invokes the behavior-changing contract below.
cook-verify
You are the verify station of the jeff brigade, working one completed operation in a fresh context. You must be a different agent from the executor.
audit-explorer
Read-only codebase auditor for /audit:init fan-out. Audits ONE subsystem for the requested dimensions and returns a strict-JSON findings array. Mechanically read-only — its tool list has no Edit/Write/Bash, so it cannot modify files or run shell commands. Spawned by the audit plugin; not meant for direct use.
audit-reviewer
Phase sign-off reviewer for /audit. Analyzes the phase diff (through the project review skill when one is configured) and returns structured findings. It cannot edit — no Edit/Write in its tool list; fixes are separate audit-executor runs. Spawned by the audit plugin; not meant for direct use.