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/omermaksutii/rugproof/notify-slackgit clone --depth 1 https://github.com/omermaksutii/RugProofWrote 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/omermaksutii/rugproof/notify-slack)<a href="https://agentmods.dev/commands/omermaksutii/rugproof/notify-slack"><img src="https://agentmods.dev/badge/commands/omermaksutii/rugproof/notify-slack.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.00014 | $0.00535 |
| Opus 5 | $0.00007 | $0.00267 |
| Sonnet 5 | $0.00003 | $0.00107 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
notify-slack scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. POST to webhook via `curl`. Bash command pattern: What it actually says
/notify-slack — push findings to Slack
Sends a compact summary of the most recent audit to a Slack channel. Use after /audit when collaborating with a team.
Setup
Create an incoming webhook in your Slack workspace: https://api.slack.com/messaging/webhooks
Then either:
- Pass
--webhook-urlto this command, or - Set
SLACK_WEBHOOK_URLin.env, or - Add to
.rugproof.yml:notifications: slack: webhook_url: "https://hooks.slack.com/services/T..../B..../...."
Procedure
- Locate the latest findings JSON (default
rugproof-reports/findings.json). - Filter by
--severity-filter(default: critical + high). - Build a Slack Block Kit payload:
{ "blocks": [ { "type": "header", "text": { "type": "plain_text", "text": "🛡 Rugproof — VulnerableVault.sol" } }, { "type": "section", "fields": [ { "type": "mrkdwn", "text": "*Critical:* 2" }, { "type": "mrkdwn", "text": "*High:* 4" }, { "type": "mrkdwn", "text": "*Grade:* F" }, { "type": "mrkdwn", "text": "*Top:* Reentrancy in withdraw()" } ]} ] } - POST to webhook via
curl. Bash command pattern:curl -X POST -H 'content-type: application/json' \ --data @payload.json \ "$SLACK_WEBHOOK_URL" - Confirm 200 response or report the failure.
Output
✓ posted 6 findings to Slack
channel: #security
permalink: https://acme.slack.com/archives/...
Notes
- Don't paste contract source into Slack. Findings + IDs only.
- For Critical findings, prefix the message with
<!channel>to ping the security on-call (configurable). - Webhook URLs are secrets — never commit to a repo. Use
.envor.rugproof.local.yml.
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 · 64 lines · 14 tokens per session scan A f80484116752
notify-slack is a command published in the GitHub repository omermaksutii/RugProof (9 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 535 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
phase6-start
Command "phase6-start" from kota1026/quantum-shield, covering phase 6 $arguments 開始, step 1: 進捗状況を確認, step 2: 未完了画面を特定, step 3: 必須ファイルを読み込む and step 4: インフラ確認.
codespace-verify
Command "codespace-verify" from kota1026/quantum-shield, covering codespaces ui確認コマンド, 1. codespaces起動確認, サービス起動状態確認, postgresql, redis, rabbitmqが起動していない場合 and フロントエンド起動.
pr-merge
Command "pr-merge" from kota1026/quantum-shield, covering pr作成・マージコマンド, 1. 変更確認, 2. コミット(未コミットがある場合), 3. pr作成 and 4. マージ.
kh_template_list
Command "kh_template_list" from KeeperHub/keeperhub, covering kh template list, examples, options, options inherited from parent commands and see also.
kh_chain
Command "kh_chain" from KeeperHub/keeperhub, covering kh chain, examples, options, options inherited from parent commands and see also.
kh_config_get
Command "kh_config_get" from KeeperHub/keeperhub, covering kh config get, examples, options, options inherited from parent commands and see also.