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 commands/outsystems/outsystems-mcp/outsystems-feedbackgit 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/commands/outsystems/outsystems-mcp/outsystems-feedback)<a href="https://agentmods.dev/commands/outsystems/outsystems-mcp/outsystems-feedback"><img src="https://agentmods.dev/badge/commands/outsystems/outsystems-mcp/outsystems-feedback.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.00000 | $0.03677 |
| Opus 5 | $0.00000 | $0.01839 |
| Sonnet 5 | $0.00000 | $0.00735 |
| Haiku 4.5 | $0.00000 | $0.00368 |
Grade A, and why
outsystems-feedback 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 yesterday.
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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The user typed /outsystems-feedback $ARGUMENTS. They want to report something about the OutSystems agent experience (a bug, a thumbs-up / thumbs-down, a comment about a tool that misbehaved, etc.).
Optional flags (direct mode only)
Parse and strip leading flags from $ARGUMENTS before deciding the mode:
--dry-run-- Show the exact feedback tool call that WOULD be made (name, value, rationale, agent_context, mentor_session_id, mentor_turn_id, experiment_id) as a code block, but do NOT invoke the tool. Reply with the preview and ask the user to confirm ("send it? [y / n]") before firing. On "n" or silence, do not send and say "OK, discarded."--quiet-- Fire the feedback call as normal but skip the confirmation narration on success. Onstatus: "accepted", reply with a single-word acknowledgment ("sent.") instead of the full "Thanks..." block. Errors andnot_configuredstill surface with their normal text. Useful for CI-driven or scripted callers.
Both flags may be combined (--dry-run --quiet shows the preview without narration decoration). Flags are only recognized in direct mode; the guided-form flow ignores them.
Two modes
Decide the mode from $ARGUMENTS (after stripping leading flags above):
- Direct mode --
$ARGUMENTSis non-empty and contains at least one non-whitespace character. The message body is whatever is left. Skip the guided-form steps and go straight to redaction + tool call. - Guided-form mode --
$ARGUMENTSis empty or whitespace-only. Do NOT reply with an error. Drive the guided form below so the user picks values instead of typing them. This is the closest thing plugins have to Claude Code's built-in/feedbackmodal.
Guided-form mode
Run these steps IN ORDER. Do not batch them into one AskUserQuestion call -- the two picker steps need to happen in sequence so the user's category choice is visible before they type the message.
Step 1 -- category picker. Call AskUserQuestion exactly once:
question: "What kind of feedback would you like to send?"header: "Category"multiSelect: falseoptions(in this order, each with a concrete example to help disambiguate):label: "Thumbs up" --description: "Something worked well or is delightful. Example: 'the mentor turn was fast and the OML edit was exactly what I wanted'."label: "Thumbs down" --description: "Something felt off but is not a full bug. Example: 'the deploy took 3 minutes, felt slow' or 'the output was correct but not what I hoped for'."label: "Bug report" --description: "Something is broken and should not be. Example: 'the publish call returned OS-BEW-1234 and never recovered'."label: "Feature request" --description: "You would like the OutSystems agent to do something it does not currently do. Example: 'I want an env-diff tool that compares two environments'."
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.
- yesterday Changed · -1 lines 50bf155e709f
- 5d ago First seen · 152 lines · 0 tokens per session scan A bf5b79660735
outsystems-feedback is a command published in the GitHub repository OutSystems/outsystems-mcp (25 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,677 tokens. 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-30.
Other commands, from other repositories
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.
history
List past OCR review sessions.
layout
Audit pipeline: choose how the manifest is stored — sharded (an index plus one file per phase: fewer tokens per phase run, parallel-safe across worktrees) or single-file (one file, one diff, no index). A layout CHOICE, not a version upgrade: both shapes are current, neither goes out of date, and this command moves in…
usage
Audit pipeline: token spend attributed by phase, task, model, author and time — with cache economics, cost-per-task and a usage trend. Read-only (never mutates the manifest).
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.