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/codeshux/tokenwise/reportnpx skills add CodeShuX/tokenwise --skill reportgit clone --depth 1 https://github.com/CodeShuX/tokenwiseWhat 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.00068 | $0.00895 |
| Opus 5 | $0.00034 | $0.00447 |
| Sonnet 5 | $0.00014 | $0.00179 |
| Haiku 4.5 | $0.00007 | $0.00089 |
Grade A, and why
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 yesterday.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tokenwise:report — Session routing report
Print a routing report for the current Claude Code session.
Steps
-
Locate the log file:
- Default:
./.tokenwise/log.ndjson(current project) - If user provides a path via
$ARGUMENTS(e.g./tokenwise:report /path/to/log.ndjson), use that
- Default:
-
If the file doesn't exist:
No TokenWise log found at <path>. Possible reasons: 1. TokenWise hasn't logged any routed tasks yet — run a few tasks first 2. You're in a different project than the one with the log 3. TokenWise install didn't write the routing rules — check ~/.claude/CLAUDE.md for the "BEGIN TokenWise" marker See: /tokenwise:install -
Determine current session:
- Look at the most recent contiguous block of log entries with the same
session_id - If
$ARGUMENTScontains--session <id>, use that session_id instead
- Look at the most recent contiguous block of log entries with the same
-
Aggregate per model:
- Group entries by
model_used - Sum
input_tokens,output_tokens,cost_actual_usd,cost_baseline_usd,savings_usd - Count tasks per model
- Group entries by
-
Print the report:
TokenWise Session Report
========================
Session ID: <id>
Started: <ts of first entry>
Duration: <wall time>
Tasks routed: <total count>
Per model:
Haiku <count> tasks <input_sum> input / <output_sum> output → $<cost_sum>
Sonnet <count> tasks <input_sum> input / <output_sum> output → $<cost_sum>
Opus <count> tasks <input_sum> input / <output_sum> output → $<cost_sum>
Fable <count> tasks <input_sum> input / <output_sum> output → $<cost_sum>
Total spent: $<total>
Baseline (all-Opus): $<baseline>
Savings: $<savings> (<pct>%)
Quality flags:
Reclassifications: <count> (<top reason>)
User overrides: <count>
Regressions: <count if logged, else "—">
Pricing snapshot:
Fable 5 $10 / $50 per 1M tokens
Opus 4.7 $5 / $25
Sonnet 4.6 $3 / $15
Haiku 4.5 $1 / $5
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.
- yesterday First seen · 82 lines · 68 tokens per session scan A 179c2841092b
report is a skill published in the GitHub repository CodeShuX/tokenwise (3 stars, last pushed 6d ago), licensed MIT. It adds 68 tokens to every session and 895 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
archify
Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and…
vox-director
Turn ONE topic into a finished Vox-style paper-collage explainer / ad video, end to end on the Atlas Cloud API + local ffmpeg — script, collage keyframes, motion, voice-over, music, captions, all automated. Use this whenever the user wants a "Vox style" video, a paper/torn-paper collage animation, a "motion collage"…
social-post
學習使用者的 Facebook／Instagram／YouTube／Threads／X 語氣與受眾，規劃、撰寫、確認後發佈內容；以已登入 Chrome 受控掃描、草擬及回覆 FB／IG／Threads 留言；並作為流量、留存與轉化的結構化帳本。使用者說「發文」「用我的口氣」「回覆留言」「自動回留言」「掃留言」「查流量」「演算法」「把數據訓練進去」「比較貼文」「優化 pattern」時使用。.
privacy-jp
日本サービス向け（일본 서비스용） プライバシーポリシー・利用規約・同意モーダル・Cookieバナー 자동 생성. 個人情報保護法(APPI)·消費者契約法·特定商取引法 반영. Next.js 1316 프로젝트 대상.
higgsfield
Use this skill whenever the user asks anything about Higgsfield AI — writing or refining video/image prompts, choosing a model (Kling, Sora 2, Veo, Wan, Seedance, Minimax Hailuo, DoP, Soul, Nano Banana, Seedream, Flux, GPT Image, etc.), camera controls, named motion presets, Soul ID character consistency, Cinema…
higgsfield-camera
Use when the user asks about camera movements, shot types, or how to describe camera behavior in a Higgsfield prompt. Contains all named camera controls with descriptions, best use cases, and example prompt phrases.