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/release)<a href="https://agentmods.dev/commands/garniergeorges/claude-presence/release"><img src="https://agentmods.dev/badge/commands/garniergeorges/claude-presence/release/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/release"><img src="https://agentmods.dev/badge/commands/garniergeorges/claude-presence/release.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.00011 | $0.00132 |
| Opus 5.5 | $0.00004 | $0.00053 |
| Sonnet 5.5 | $0.00002 | $0.00026 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
release 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 resource_release tool with:
session_id: this session's id (fromsession_register).project: the project's absolute path.resource: the resource name from$ARGUMENTS.
If $ARGUMENTS is empty, first call resource_list for this project, show the user the locks this session currently holds, and ask which one to release.
After release, confirm briefly and mention that other waiting sessions (if any) can now proceed.
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 · 15 lines · 11 tokens per session scan A 3b40bb4522bb
release is a command published in the GitHub repository garniergeorges/claude-presence (12 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 132 once invoked, about $0.0000 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
mcptoon-setup
Set up or repair the mcptoon CLI for this machine (install, verify, diagnose).
review
Perform a comprehensive code review with actionable feedback.
test
Generate tests for the specified code or feature.
fix
Diagnose and fix bugs, errors, and issues in code.
constitution
Update the tracked OMK project constitution at specs/constitution.md.
plan
Generate specs/[###-feature]/plan.md from the active feature specification.