Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sara-star-quant/presence/plugin install 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/sara-star-quant/presence/presence-bugreport)<a href="https://agentmods.dev/commands/sara-star-quant/presence/presence-bugreport"><img src="https://agentmods.dev/badge/commands/sara-star-quant/presence/presence-bugreport/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/sara-star-quant/presence/presence-bugreport"><img src="https://agentmods.dev/badge/commands/sara-star-quant/presence/presence-bugreport.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.00039 | $0.00184 |
| Opus 5 | $0.00019 | $0.00092 |
| Sonnet 5 | $0.00008 | $0.00037 |
| Haiku 4.5 | $0.00004 | $0.00018 |
Grade A, and why
presence-bugreport 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 8d 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
Run the presence bug-report bundler and display its output verbatim. Then tell the user to paste the output into the issue template at https://github.com/sara-star-quant/presence/issues/new?template=bug.yml in the "Output of ..." field.
PRESENCE_ROOT="${CLAUDE_PLUGIN_ROOT:-$(realpath ~/.claude/plugins/presence 2>/dev/null || echo .)}"
PYTHONPATH="$PRESENCE_ROOT/lib" python3 "$PRESENCE_ROOT/lib/bugreport.py" --md --cwd "$PWD"
This is a read-only command. It does not modify any state.
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.
- 8d ago First seen · 14 lines · 39 tokens per session scan A dfa35b61dfcf
presence-bugreport is a command published in the GitHub repository sara-star-quant/presence (7 stars, last pushed 2d ago), licensed Apache-2.0. It adds 39 tokens to every session and 184 once invoked, about $0.0002 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-31.
Other commands, from other repositories
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
investigate
Systematic root-cause debugging — find the cause before writing any fix.
diagnose
Run a self-check on your AI Brain Starter install (CLAUDE.md, Meta folder, skills, hooks, MCPs).
ccc-debug-session
Start a structured debug session with hypothesis tracking and resolution documentation.
scan
A codebase onboarding briefing that examines a new project's files, tools, main entry points, and marked technical debt.
diagnose
Trace a failed or stalled pipeline run — identify which FORGE annotation is missing or malformed, diagnose the failure point, and suggest specific remediation steps.