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 skills add shwilliamson/automatasaurus --skill notificationsgit clone --depth 1 https://github.com/shwilliamson/automatasaurusWrote 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/skills/shwilliamson/automatasaurus/notifications)<a href="https://agentmods.dev/skills/shwilliamson/automatasaurus/notifications"><img src="https://agentmods.dev/badge/skills/shwilliamson/automatasaurus/notifications/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/skills/shwilliamson/automatasaurus/notifications"><img src="https://agentmods.dev/badge/skills/shwilliamson/automatasaurus/notifications.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.00031 | $0.00638 |
| Opus 5.5 | $0.00012 | $0.00255 |
| Sonnet 5.5 | $0.00006 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
notifications 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 2mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notification System
Automatasaurus includes a notification system to alert the user when their attention is needed.
Automatic Notifications
The system automatically sends notifications on stop based on context:
- Questions: When Claude asks a question and waits for input
- Approvals: When approval is needed to proceed
- Stuck: When an agent encounters an issue
- Complete: When all work is done
Explicit Notification Request
When you need to explicitly alert the user, use:
.claude/hooks/request-attention.sh <type> "<message>"
Notification Types
| Type | When to Use | Sound |
|---|---|---|
question |
You have a question that needs answering | Submarine |
approval |
You need approval before proceeding | Submarine |
stuck |
You've encountered an issue you can't resolve | Basso (alert) |
complete |
All assigned work is finished | Hero (success) |
info |
General notification | Glass |
error |
An error occurred | Basso (alert) |
Examples
# Question needs answering
.claude/hooks/request-attention.sh question "Should I use PostgreSQL or MySQL for this project?"
# Approval needed
.claude/hooks/request-attention.sh approval "PR #42 is ready for review"
# Got stuck
.claude/hooks/request-attention.sh stuck "Cannot access the GitHub API - authentication failed"
# Work complete
.claude/hooks/request-attention.sh complete "All 5 user stories have been implemented and tested"
# Error occurred
.claude/hooks/request-attention.sh error "Build failed with 3 errors"
When to Notify
Always Notify For:
- Questions that block progress
- Security-related approvals
- When you've been stuck for more than one attempt
- Completion of significant milestones
- Errors that require human intervention
Don't Notify For:
- Minor progress updates
- Self-recoverable errors
- Questions you can answer from context
Configuration
Notifications can be configured via environment variables:
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.
- 2mo ago First seen · 96 lines · 31 tokens per session scan A b56e4d7731df
notifications is a skill published in the GitHub repository shwilliamson/automatasaurus (5 stars, last pushed 8mo ago), licensed MIT. It adds 31 tokens to every session and 638 once invoked, about $0.0001 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-08-31.
notifications compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| notificationsshwilliamson/automatasaurus | Skill | 5 | 8mo ago | MIT | A | 31 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |