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/dmzoneill/redhat-ai-workflow/notify-mrgit clone --depth 1 https://github.com/dmzoneill/redhat-ai-workflowWrote 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/dmzoneill/redhat-ai-workflow/notify-mr)<a href="https://agentmods.dev/commands/dmzoneill/redhat-ai-workflow/notify-mr"><img src="https://agentmods.dev/badge/commands/dmzoneill/redhat-ai-workflow/notify-mr.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.00939 |
| Opus 5 | $0.00000 | $0.00469 |
| Sonnet 5 | $0.00000 | $0.00188 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
notify-mr 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 5d 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.
/notify-mr
Post a review request to the team Slack channel for an existing MR.
Overview
Post a review request to the team Slack channel for an existing MR.
Underlying Skill: notify_mr
This command is a wrapper that calls the notify_mr skill. For detailed process information, see skills/notify_mr.md.
Arguments
| Argument | Required | Description |
|---|---|---|
mr_id |
No | - |
Usage
Examples
skill_run("notify_mr", '{"mr_id": "$MR_ID"}')
# Notify about specific MR
skill_run("notify_mr", '{"mr_id": "1459"}')
# From current branch (auto-detect MR)
skill_run("notify_mr", '{}')
# With custom message
skill_run("notify_mr", '{"mr_id": "1459", "message": "Addressed all feedback, ready for final review"}')
# Send as reminder
skill_run("notify_mr", '{"mr_id": "1459", "reminder": true}')
# With specific project
skill_run("notify_mr", '{"mr_id": "1459", "project": "automation-analytics/automation-analytics-backend"}')
🔀 *MR Ready for Review*
📋 *Jira:* AAP-61661 - Fix billing calculation
🔗 *MR:* !1459 - AAP-61661 - Fix billing calculation
📁 *Repo:* automation-analytics-backend
Please review when you have a moment 🙏
Process Flow
This command invokes the notify_mr skill. The process flow is:
flowchart LR
START([User runs /notify-mr]) --> VALIDATE[Validate Arguments]
VALIDATE --> CALL[Call notify_mr skill]
CALL --> EXECUTE[Execute Skill Steps]
EXECUTE --> RESULT[Return Result]
RESULT --> END([Complete])
style START fill:#6366f1,stroke:#4f46e5,color:#fff
style END fill:#10b981,stroke:#059669,color:#fff
style CALL fill:#3b82f6,stroke:#2563eb,color:#fff
```text
For detailed step-by-step process, see the [notify_mr skill documentation](../skills/notify_mr.md).
## Details
## Instructions
```text
skill_run("notify_mr", '{"mr_id": "$MR_ID"}')
When to Use
- After creating a draft MR that's now ready
- To remind the team about a pending review
- When you marked an MR as ready after initial work
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.
- 5d ago First seen · 138 lines · 0 tokens per session scan A 87ab71a2e117
notify-mr is a command published in the GitHub repository dmzoneill/redhat-ai-workflow (5 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 939 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-31.
Other commands, from other repositories
OPSX: Onboard
Guided onboarding - walk through a complete OpenSpec workflow cycle with narration.
OPSX: Bulk Archive
Archive multiple completed changes at once.
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
OPSX: New
Start a new change using the experimental artifact workflow (OPSX).
workflow
Command "workflow" from n8n-io/n8n, covering workflow, workflow list, workflow get, workflow create and workflow update.