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/sorbh/claude-selfaware/selfaware-usage-infogit clone --depth 1 https://github.com/Sorbh/claude-selfawareWrote 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/sorbh/claude-selfaware/selfaware-usage-info)<a href="https://agentmods.dev/commands/sorbh/claude-selfaware/selfaware-usage-info"><img src="https://agentmods.dev/badge/commands/sorbh/claude-selfaware/selfaware-usage-info.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 | $0.00013 | $0.00136 |
| Opus 5 | $0.00006 | $0.00068 |
| Sonnet 5 | $0.00003 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
selfaware-usage-info 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 4d 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 ~/.claude/skills/selfaware/scripts/usage-check.sh and summarize my current usage.
Report: 5-hour %, 7-day %, minutes until reset, whether Codex is available for offload,
and whether I should go full speed, delegate to Codex, or wrap up.
Then run ~/.claude/skills/selfaware/scripts/usage-info.sh for the visual dashboard.
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.
- 4d ago First seen · 9 lines · 13 tokens per session scan A c9d79e7e2c6f
selfaware-usage-info is a command published in the GitHub repository Sorbh/claude-selfaware (2 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 136 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-31.
Other commands, from other repositories
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
deps-age
Analyze dependency freshness and maintenance activity.
setup
Diagnose-first project setup with state machine — scans, confirms, interviews, writes.