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/garniergeorges/claude-presence/claimgit 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/claim)<a href="https://agentmods.dev/commands/garniergeorges/claude-presence/claim"><img src="https://agentmods.dev/badge/commands/garniergeorges/claude-presence/claim.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.00016 | $0.00217 |
| Opus 5 | $0.00008 | $0.00109 |
| Sonnet 5 | $0.00003 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
claim 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 6d 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_claim tool.
Parse $ARGUMENTS:
- The first word is the resource name (e.g.
ci,deploy:staging,port:3000,db:staging). - The rest of the line, if any, is the reason.
Use the current session's session_id (the one you used at session_register) and the project's absolute path.
If the result is ok: true, confirm briefly: lock acquired, TTL, when to release.
If the result is ok: false:
- Report who holds the lock, their branch, and their intent if available.
- Do NOT proceed with the shared operation.
- Ask the user whether to wait, to use broadcast to coordinate, or to abort.
If $ARGUMENTS is empty, ask the user which resource to claim.
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.
- 6d ago First seen · 22 lines · 16 tokens per session scan A 781c2d4d41a3
claim is a command published in the GitHub repository garniergeorges/claude-presence (12 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 217 once invoked, about $0.0001 per session on Opus 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
optimize
Optimize code for performance, bundle size, or resource usage.
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.
plan
Generate specs/[###-feature]/plan.md from the active feature specification.
constitution
Update the tracked OMK project constitution at specs/constitution.md.