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 AleksandarBisevac/claude-plugins/plugin install auditWrote 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/aleksandarbisevac/claude-plugins/audit-spend)<a href="https://agentmods.dev/skills/aleksandarbisevac/claude-plugins/audit-spend"><img src="https://agentmods.dev/badge/skills/aleksandarbisevac/claude-plugins/audit-spend/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/skills/aleksandarbisevac/claude-plugins/audit-spend"><img src="https://agentmods.dev/badge/skills/aleksandarbisevac/claude-plugins/audit-spend.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.00072 | $0.00448 |
| Opus 5 | $0.00036 | $0.00224 |
| Sonnet 5 | $0.00014 | $0.00090 |
| Haiku 4.5 | $0.00007 | $0.00045 |
Grade A, and why
audit-spend 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 10d 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
What the work cost
Read ${CLAUDE_PLUGIN_ROOT}/commands/usage.md and follow it. This file only exists so the
question finds the command.
The free first move
/audit:usage --backfill needs no manifest, no setup and no agents. It reads the
transcripts already on disk and attributes past spend by phase, task, model, author and
day. If someone is asking what things cost, run this — do not first propose installing a
pipeline. It is the cheapest true answer available and it uses data they already have.
What this answers that /cost does not
/cost and /stats are session-scoped totals. This is spend attributed to plan units —
which phase, which task, which model, which person, with cache economics and cost-per-task.
Native OpenTelemetry has no phase or task in its attribute set, so this is not a nicer
rendering of the same numbers; it is a different join.
Print it, do not re-render it
audit-usage.py renders its own ASCII output. Print it verbatim. Laying the tables out
again costs tokens to answer a question about token cost, which is self-defeating — the
command file says this too, and it is the rule the rest of this plugin's output follows.
When a number would be a guess, there will not be one
If you are asked something the ledger cannot support — whether a cheaper model would do, what the next phase will cost — check what the output actually says. The routing advisory stays silent without enough in-repo evidence, and projections are suppressed below a sample gate. That silence is the answer, not a gap to fill in with a price list.
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.
- 10d ago First seen · 37 lines · 72 tokens per session scan A 8c1af97f7baa
audit-spend is a skill published in the GitHub repository AleksandarBisevac/claude-plugins (4 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 448 once invoked, about $0.0004 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
party
Throw or join an agents-party: a shared channel where several AI agent sessions (and their humans) talk to each other — Claude Code, Cursor, Codex or any other agent, on one machine or across machines. Use when the user asks to throw or start a party, wants several agent sessions to collaborate in one chat, wants two…
validate-album
Validates album directory structure, file locations, and content integrity. Use before release or whenever the user wants to check an album's structural health.
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
import-art
Places album art files in the correct audio and content directory locations. Use when the user has generated or downloaded album artwork that needs to be saved.
plagiarism-checker
Scans lyrics for phrases that may match existing songs using web search and LLM knowledge. Use before release to check for unintentional borrowing.
cleanup
Clean up after a merged pull request — return to the base branch, remove the worktree, delete the branch, sweep other stale branches and worktrees, and report tracker state. Use after a merge or whenever asked what is left over.