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 skills/krishnesh7/claude-usage-analytics/vs-session-reportnpx skills add krishnesh7/claude-usage-analytics --skill vs-session-reportgit clone --depth 1 https://github.com/krishnesh7/claude-usage-analyticsWrote 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/skills/krishnesh7/claude-usage-analytics/vs-session-report)<a href="https://agentmods.dev/skills/krishnesh7/claude-usage-analytics/vs-session-report"><img src="https://agentmods.dev/badge/skills/krishnesh7/claude-usage-analytics/vs-session-report.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.00058 | $0.00260 |
| Opus 5 | $0.00029 | $0.00130 |
| Sonnet 5 | $0.00012 | $0.00052 |
| Haiku 4.5 | $0.00006 | $0.00026 |
Grade A, and why
vs-session-report 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
Display the full feature comparison between claude-usage-tracker and the official session-report plugin.
Run the following command and render the output as formatted Markdown:
cat "${CLAUDE_PLUGIN_ROOT}/docs/COMPARISON.md"
After displaying it, summarise the three most relevant differences for the user's specific situation:
- If they mentioned cost / money / dollars → lead with cost imputation + persistent history
- If they mentioned project / product → lead with named project registry + CLAUDE_USAGE.md
- If they mentioned history / all time / last month → lead with SQLite persistence + unlimited time window
- If they mentioned cache → lead with the enrichment pipeline section
- Default → lead with the at-a-glance table and the "when to use which" section
Do not recommend removing session-report — the two plugins are complementary.
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 · 32 lines · 58 tokens per session scan A 6e1834bb43e7
vs-session-report is a skill published in the GitHub repository krishnesh7/claude-usage-analytics (2 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 260 once invoked, about $0.0003 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 skills, from other repositories
link-ticket-to-session
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma. Use when the user explicitly asks to link, attach, associate, or connect this session to a ticket, issue, or PR — e.g. "/link-ticket-to-session ABC-123", "link this session to…
craft-style
Builds a personal output style on hush's frame — the user's voice on the surface, hush's silence-and-structure mechanics copied verbatim underneath. Manages its own creations: lists them alongside stock Hush and edits them. A mechanical verifier confirms every invariant survived. Activation is hush:pick-style's job …
pick-style
Lists every output style available to this plugin — stock Hush and anything craft-style has built — and switches the active one. Activation swaps the chosen style into the plugin's own slot so it binds like stock, and hands back to stock on request. This skill owns the swap procedure; craft-style calls into it. Only…
fleet-doctrine
Fleet Deck doctrine — how to behave as one Claude Code session among many on this machine. Use when you see [FLEETDECK] messages in context, when told to coordinate with / message / answer another session, when asked about the fleet board, or when deputized to decide something for another session.
Capacity, Performance & Cost Assumptions
Ensure architecture/design docs state traffic assumptions, performance budgets, resource limits, and cost risks for critical paths.
provisioning-wizard
Bash wizard for human-only setup.