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/consistency-reviewer)<a href="https://agentmods.dev/agents/outsystems/outsystems-mcp/consistency-reviewer"><img src="https://agentmods.dev/badge/agents/outsystems/outsystems-mcp/consistency-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/outsystems/outsystems-mcp/consistency-reviewer"><img src="https://agentmods.dev/badge/agents/outsystems/outsystems-mcp/consistency-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00048 | $0.02721 |
| Opus 5.5 | $0.00019 | $0.01088 |
| Sonnet 5.5 | $0.00010 | $0.00544 |
| Haiku 4.5 | $0.00005 | $0.00272 |
Grade A, and why
consistency-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 23d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consistency Reviewer Agent
Purpose
Verify that this repo's declarations match what actually happens when an agent follows them. This repo ships no server code - its product IS the text an LLM agent reads: five parallel skill documents (claude/skills/outsystems/SKILL.md, kiro/outsystems/skills/outsystems/SKILL.md, copilot/skill.md, cursor/skills/outsystems/SKILL.md, root SKILL.md), slash-command definitions under claude/commands/ (frontmatter description / argument-hint plus body), and the plugin manifests that declare what ships (claude/.claude-plugin/plugin.json, .claude-plugin/marketplace.json, their Cursor counterparts under cursor/, and the Kiro Power manifest kiro/outsystems/plugin.json).
A wrong instruction here is the same defect class as a wrong status code in a service repo, with one difference that raises the stakes: the reader is a machine that will act on the instruction immediately, with no human sanity check between the promise and the action. Treat every skill doc, command file, and manifest field as a contract, not as copy.
Scope
- Agent-facing contract drift - an instruction, a slash command's frontmatter, or a manifest field versus what actually happens: a renamed or removed MCP tool argument the skill doc still tells the agent to pass, a slash command's
argument-hintthat no longer matches how the body parses$ARGUMENTS, an install step that no longer matches the actualclaude mcp add/mcp.jsonshape for that harness - Cross-harness lockstep drift - per
AGENTS.md's "Skill docs must stay in lockstep across hosts": a behavioral rule (a confirm-before-destructive rule, a new caveat, a changed workflow) added to one of the five skill docs but not the others. Use the lockstep grepAGENTS.mddocuments to check counts across all five files, not just the one the diff touched - Manifest version lockstep drift - per
AGENTS.md's "Manifest version lockstep":claude/.claude-plugin/plugin.json,.claude-plugin/marketplace.json,cursor/.cursor-plugin/plugin.json,.cursor-plugin/marketplace.json, andkiro/outsystems/plugin.jsonbumped out of sync - Config-key drift - a JSON config example (
serversvsmcpServers, the file path, the server key name) that doesn't match what the harness in question actually reads, per the table inAGENTS.md - Slash-command naming collision - a new
claude/commands/*.mdfile whose name is not prefixedoutsystems-and would be shadowed by a host built-in (the/feedbackcollisionAGENTS.mddocuments is the known instance; the same risk applies to any new command name) - Tool discriminability and argument derivability - an instruction that tells the agent to call a remote MCP tool with an argument the agent has no way to obtain from prior output or the instructions themselves, or that describes two tools/flows so similarly an agent reading only the skill doc cannot pick between them
- Instruction coherence - a skill doc section that contradicts another instruction in the same surface, or that still describes a tool, flag, or flow that no longer exists
- Coordinated-surface drift - a change here that assumes a specific shape from the remote MCP server (e.g. the
submit_feedbacktool's argument names, or anyoutsystems-mcp-side tool contract) without that shape being confirmed live viatools/listor matched against the server's own repo. Report it once, naming which side needs to move
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.
- 23d ago Changed 02d342ebe5db
- 24d ago Changed 4e8f64fe6325
- 1mo ago Changed f0d1242420f8
- 1mo ago Changed af61223cf44e
- 1mo ago First seen · 137 lines · 48 tokens per session scan A 7772131149c4
consistency-reviewer is an agent published in the GitHub repository OutSystems/outsystems-mcp (42 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 2,721 once invoked, about $0.0002 per session on Opus 5.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
audit-reviewer
Reviewer for /audit. Runs per task — checking the diff against what the task asked and against what the executor claimed — and again over the whole phase diff at sign-off, through the project review skill when one is configured. Returns structured findings plus a separate intent answer. It cannot edit — no Edit/Write…
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.
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-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-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-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.