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-teamgit 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-team)<a href="https://agentmods.dev/commands/dmzoneill/redhat-ai-workflow/notify-team"><img src="https://agentmods.dev/badge/commands/dmzoneill/redhat-ai-workflow/notify-team.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.00611 |
| Opus 5 | $0.00000 | $0.00305 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
notify-team 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/notify-team
Send a message to a Slack channel.
Overview
Send a message to a Slack channel.
Underlying Skill: notify_team
This command is a wrapper that calls the notify_team skill. For detailed process information, see skills/notify_team.md.
Arguments
| Argument | Required | Description |
|---|---|---|
channel |
No | - |
message |
No | - |
Usage
Examples
skill_run("notify_team", '{"channel": "$CHANNEL", "message": "$MESSAGE"}')
# Simple notification
skill_run("notify_team", '{"channel": "analytics-dev", "message": "Deploying v1.2.3 to stage"}')
# With mentions
skill_run("notify_team", '{"channel": "analytics-dev", "message": "Need review on AAP-61214", "mentions": ["daoneill"]}')
Process Flow
This command invokes the notify_team skill. The process flow is:
flowchart LR
START([User runs /notify-team]) --> VALIDATE[Validate Arguments]
VALIDATE --> CALL[Call notify_team 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_team skill documentation](../skills/notify_team.md).
## Details
## Instructions
```text
skill_run("notify_team", '{"channel": "$CHANNEL", "message": "$MESSAGE"}')
What It Does
- Finds the Slack channel
- Posts the message
- Optionally mentions users
Options
| Parameter | Description | Default |
|---|---|---|
channel |
Channel name (without #) | Required |
message |
Message to send | Required |
mentions |
List of usernames to @mention | Optional |
Additional Examples
# Simple notification
skill_run("notify_team", '{"channel": "analytics-dev", "message": "Deploying v1.2.3 to stage"}')
# With mentions
skill_run("notify_team", '{"channel": "analytics-dev", "message": "Need review on AAP-61214", "mentions": ["daoneill"]}')
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 · 97 lines · 0 tokens per session scan A 697b9a759c2d
notify-team 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 611 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.