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 5dive-ai/5dive-plugins --skill notify-usergit clone --depth 1 https://github.com/5dive-ai/5dive-pluginsWrote 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/5dive-ai/5dive-plugins/notify-user)<a href="https://agentmods.dev/skills/5dive-ai/5dive-plugins/notify-user"><img src="https://agentmods.dev/badge/skills/5dive-ai/5dive-plugins/notify-user/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/5dive-ai/5dive-plugins/notify-user"><img src="https://agentmods.dev/badge/skills/5dive-ai/5dive-plugins/notify-user.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.00071 | $0.01300 |
| Opus 5.5 | $0.00028 | $0.00520 |
| Sonnet 5.5 | $0.00014 | $0.00260 |
| Haiku 4.5 | $0.00007 | $0.00130 |
Grade A, and why
notify-user 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 1mo 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
notify-user — Telegram comms playbook (Antigravity edition)
You're paired with a Telegram chat via the telegram-agy MCP plugin's
bot. The user reads only what reaches the chat — anything you print
to stdout or stderr never gets to them. Every inbound Telegram message
MUST get a reply via the MCP tool before your turn ends, even if it's
just "Done."
The loop is simple: wait_for_message → do the work → reply →
wait_for_message again.
Cadence
- Inbound → ack <5s. Send a short "on it"
replybefore starting any non-trivial work. The Telegram-paired user has no other signal that you received the message. - Long work → edit only if you're still the latest message. Use
edit_messagefor progress updates so the user's phone doesn't buzz on every tick — but only if your previous reply is still the newest message in the chat. If a fresher message exists (a new inbound from the user, or another reply you sent in between), the edit will be missed in scrollback; send a newreplyinstead. - Done or blocked → new
reply. A fresh reply triggers a push notification;edit_messagedoes not. - Silence ceiling: ~60s. Beyond that the user starts assuming the bridge broke. Send a short edit or new reply (per the latest-message rule above) even mid-work if a substantive reply is still >60s away. The silence-watchdog hook will also ping the user after 120s of tool calls without a reply — that's a safety net, not something to rely on.
- Default
timeout_seconds=50forwait_for_message. Antigravity kills any MCP tool call past itsMCP tool timeout(default 60s), so higher timeouts drop messages arriving near the boundary. If<telegram timeout=true/>comes back, END YOUR TURN; do not re-callwait_for_messageto keep polling. The server re-arms you when the next message is queued.
Hard rules
- Reply via the
replyMCP tool, not stdout. Plain text in your turn output is invisible to the Telegram user. - Don't auto-delegate on acknowledgements. Phrases like "you can
talk now", "go ahead", "say something" mean "the channel works,
please respond" — they are NOT requests to involve another agent.
Reply via
reply. Inter-agent handoff (via the5dive-cliskill if installed) is appropriate only when the user explicitly asks for it ("ask scout to do this", "hand off to marketing"). - Don't reply to chats you weren't messaged from. The server
rejects
chat_idvalues outside its allowlist; always sourcechat_idfrom a priorwait_for_messageresult.
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.
- 1mo ago First seen · 108 lines · 71 tokens per session scan A 88c7137f3fe6
notify-user is a skill published in the GitHub repository 5dive-ai/5dive-plugins (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 71 tokens to every session and 1,300 once invoked, about $0.0003 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.
Other skills, from other repositories
aident-loadout
Run multi-step work across apps the user connected in Aident Loadout: live action schemas, connection checks, cost preflight, and approval before side effects.
jobs
Manage agy staffer background jobs - collect results, check status, cancel, follow-up conversation, and setup. Use when an agy job needs collecting, when the user asks "is the agy job done", "show agy's result", "cancel the agy job", "continue the agy conversation", or "set up agy". This is the orchestrator's skill…
onboarding-express
AI-guided architectural tour of any codebase — entry points, business logic, and the most complex module in one structured pass, powered by Graph-It-Live. Use this skill whenever someone is new to a codebase or wants a quick orientation. Trigger for: "I just joined this team", "explain this repo to me", "give me a…
agy-jobs
Manage agy staffer background jobs - collect results, check status, cancel, follow-up conversation, and setup. Use when an agy job needs collecting, when the user asks "is the agy job done", "show agy's result", "cancel the agy job", "continue the agy conversation", or "set up agy". This is the orchestrator's skill…
accint-commitments
Triage acc's open promises and close them with honest real-world verdicts via accact(runtime="outcome").
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".