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 skills add getpapi/papi --skill usage-reportergit clone --depth 1 https://github.com/getpapi/papiWrote 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/getpapi/papi/usage-reporter)<a href="https://agentmods.dev/skills/getpapi/papi/usage-reporter"><img src="https://agentmods.dev/badge/skills/getpapi/papi/usage-reporter/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/getpapi/papi/usage-reporter"><img src="https://agentmods.dev/badge/skills/getpapi/papi/usage-reporter.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.00057 | $0.00887 |
| Opus 5.5 | $0.00023 | $0.00355 |
| Sonnet 5.5 | $0.00011 | $0.00177 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
usage-reporter 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
usage-reporter
PAPI cannot see how many tokens a build used: the MCP call only sees its own request, and a model cannot read its own usage. The numbers exist in your AI client's local transcript. This skill sums them for a window and hands you the three numbers build_execute already accepts.
It is optional. If it cannot run, complete the build normally: tokens are recorded as Not recorded, never as 0 and never estimated.
What it supports today
| Client | Source | Status |
|---|---|---|
| Claude Code | ~/.claude/projects/<project path with dashes>/*.jsonl |
Verified. Every assistant message carries input, output, cache read and cache creation tokens, a timestamp and the model. |
| Codex, OpenCode | not verified | No equivalent transcript was available to check. A follow-up task exists for each client that is confirmed to write usage. Until then these report Not recorded. |
How to use it
- Note the build window:
started_atwhen you calledbuild_executeto start, and the time you complete it. - Run the script with that window (optionally with the stage windows):
node .claude/skills/usage-reporter/scripts/usage-report.mjs \
--from 2026-10-14T09:00:00Z --to 2026-10-14T11:30:00Z
- If the result has
"notRecorded": false, pass itsbuildExecuteobject into the completingbuild_executecall asinput_tokens,output_tokensandcache_read_tokens. If"notRecorded": true, pass nothing.
Stage calls (plan, review_submit, release, strategy_review): each of these tool responses ends with a line naming the time the next window opened. On your next stage call, run the script with --from <that time> --to <now> and pass its buildExecute object, your model and window_started_at as the optional stage_usage argument. The server stores it on that call, so no one runs anything by hand and nothing is estimated.
Per-stage totals: pass --stages '{"plan":["<iso>","<iso>"],"build":[...],"review":[...],"release":[...]}' using the plan, build, review and release tool-call timestamps. Stages are assigned in order without overlap; whatever falls outside every stage is reported as unassigned, so the stages plus unassigned always equal the window total.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 50 lines · 57 tokens per session scan A 70b761e9cd84
usage-reporter is a skill published in the GitHub repository getpapi/papi (11 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 887 once invoked, about $0.0002 per session on Opus 5.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-10-16.
Other skills, from other repositories
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.