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.
git clone --depth 1 https://github.com/garniergeorges/claude-presenceWrote 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/garniergeorges/claude-presence/notify)<a href="https://agentmods.dev/commands/garniergeorges/claude-presence/notify"><img src="https://agentmods.dev/badge/commands/garniergeorges/claude-presence/notify/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/commands/garniergeorges/claude-presence/notify"><img src="https://agentmods.dev/badge/commands/garniergeorges/claude-presence/notify.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.00023 | $0.00257 |
| Opus 5.5 | $0.00009 | $0.00103 |
| Sonnet 5.5 | $0.00005 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
notify 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.
What it actually says
Call the claude-presence MCP broadcast tool with to_session set and priority: 'warning' so the recipient sees it on their next prompt without calling /inbox.
Parse $ARGUMENTS:
- The first whitespace-delimited token is the recipient
session-id. - The rest is the
message. If either is missing, ask the user.
If you don't know the candidate session ids, suggest the user run /presence first.
Required args for the tool:
session_id: this session's id (fromsession_register). If unknown, ask the user to/registerfirst.project: the project's absolute path.from_branch: the current git branch if available; omit otherwise.to_session: the parsed recipient id.priority:"warning"(so the message is auto-surfaced on the recipient's next prompt).message: the parsed message string.
After posting, confirm in one line: notified <recipient> (warning, id <n>).
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 · 23 lines · 23 tokens per session scan A 5264228d57b5
notify is a command published in the GitHub repository garniergeorges/claude-presence (12 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 257 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-30.
Other commands, from other repositories
follow-up
Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…
amp-download
Command "amp-download" from agentmessaging/claude-plugin, covering /amp-download, usage, arguments, options and examples.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
dedupe
Find duplicate files (exact hash groups, or near-duplicate images) and optionally reclaim space, using the carrel CLI.
tag
Add, remove, list, or find-by tags on local files in the carrel desk database.
test
Generate tests for the specified code or feature.