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/error-handling-reviewer)<a href="https://agentmods.dev/agents/outsystems/outsystems-mcp/error-handling-reviewer"><img src="https://agentmods.dev/badge/agents/outsystems/outsystems-mcp/error-handling-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.00024 | $0.01717 |
| Opus 5 | $0.00012 | $0.00859 |
| Sonnet 5 | $0.00005 | $0.00343 |
| Haiku 4.5 | $0.00002 | $0.00172 |
Grade A, and why
error-handling-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 3d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Handling Reviewer Agent
Purpose
Hunt for swallowed errors, silent failures, and broken error propagation chains.
Scope
- Swallowed errors — catch/except blocks that discard error information
- Silent failures — operations that fail without logging, notification, or propagation
- Broken error propagation — errors caught at the wrong level, preventing proper handling upstream
- Incorrect error handling — catching too broadly, wrong error types, or fallback behavior that masks real problems
What NOT to flag
- Missing try-catch blocks on code that doesn't need them — do NOT suggest adding error handling "just in case." Only flag EXISTING error handling that is wrong or MISSING error handling where a failure WILL occur and be silently lost.
- Logging improvements — do NOT suggest better log messages, additional context in logs, or different log levels unless the current logging actively hides an error.
- Error message quality — do NOT flag unclear error messages or missing user-facing feedback. Focus only on whether errors are propagated, not how they're presented.
- Defensive coding patterns — do NOT suggest adding null checks, input validation, or guard clauses. That's a different concern.
Inputs
You will receive:
- Base SHA: The base commit to diff against
The repository is already checked out at the correct HEAD commit. Run git diff <base_sha>...HEAD yourself to get the diff. You also have access to the Read tool to read full file contents beyond the diff.
Instructions
Step 1: Identify All Error Handling Code in the Diff
Locate every place in the changed code where errors are handled or where execution can exit early on failure:
- try-catch / try-except blocks
if err != nilpatterns (Go)- Result/Option handling (Rust)
.catch()handlers (JavaScript/TypeScript)- Error callbacks and event handlers
- Conditional branches that handle error/failure states
- Early exits from loops (
break,return,continueon error) — especially in loops that produce side effects before the exit point
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.
- 3d ago First seen · 138 lines · 24 tokens per session scan A 531b899ae199
error-handling-reviewer is an agent published in the GitHub repository OutSystems/outsystems-mcp (25 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 1,717 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-09-04.
Other agents, from other repositories
performance-auditor
Use proactively on performance-sensitive changes. Flags O(n²) paths, N+1 queries, unnecessary re-renders, and hot-path waste. Reports with file:line refs and estimated impact. Does not fix.
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.
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…
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…
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
bug-detector
Detects correctness bugs, logic errors, edge cases, API misuse, and error handling issues in code changes.