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/platonai/browser4/task-token-usagenpx skills add platonai/Browser4 --skill task-token-usagegit clone --depth 1 https://github.com/platonai/Browser4What 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.00041 | $0.00718 |
| Opus 5 | $0.00020 | $0.00359 |
| Sonnet 5 | $0.00008 | $0.00144 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
task-token-usage 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Token Usage
Analyzes Claude Code conversation traces to report token consumption per task.
When to Use
- "list tasks with token usage"
- "show me token usage for each task"
- "how many tokens did task X use?"
- "what tasks ran in the last N hours?"
- "compare token usage across tasks"
How It Works
- Scans
~/.claude/projects/<project>/for JSONL session traces - Extracts
input_tokens,output_tokens,cache_read_input_tokensfrom each assistant message - Optionally matches sessions to draft task files in
coworker/tasks/issues/draft/ - Prints a summary table grouped by task
Usage
Run the bundled script:
python3 coworker/skills/task-token-usage/scripts/list-tasks.py [OPTIONS]
Options
| Flag | Description |
|---|---|
--recent N |
Only show sessions from last N hours (default: 24) |
-d, --detail |
Per-session breakdown instead of grouped summary |
-a, --all |
Show all sessions (no time filter) |
Examples
# Summary of last 12 hours
python3 coworker/skills/task-token-usage/scripts/list-tasks.py --recent 12
# Detailed per-session view for all time
python3 coworker/skills/task-token-usage/scripts/list-tasks.py --all --detail
# Default: last 24 hours, grouped summary
python3 coworker/skills/task-token-usage/scripts/list-tasks.py
Output Columns (Summary Mode)
| Column | Description |
|---|---|
| Task | Task name (matched from draft files or first step description) |
| Runs | Number of evaluation sessions for this task |
| In Tok | Total input tokens across all runs |
| Out Tok | Total output tokens across all runs |
| Cache | Total cache-read + cache-creation tokens |
| TOTAL | Sum of all tokens |
| Avg/run | Average total tokens per run |
Output Columns (Detail Mode)
| Column | Description |
|---|---|
| Time | When the session ended |
| Task | Matched task name |
| In | Input tokens |
| Out | Output tokens |
| CacheR | Cache-read tokens |
| TOTAL | Total tokens |
| Model | AI model used |
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.
- 2d ago First seen · 91 lines · 41 tokens per session scan A 30be332fe6d8
task-token-usage is a skill published in the GitHub repository platonai/Browser4 (1,114 stars, last pushed 3d ago), licensed Apache-2.0. It adds 41 tokens to every session and 718 once invoked, about $0.0002 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-30.
Other skills, from other repositories
eric-task-master
Install, connect, and use Eric Task Master for durable Playwright browser jobs with persistent or ephemeral Profiles, live fast-auto-human behavior control, task queues, progress health, semantic diagnostics, recovery, artifacts, and composable Task Packs.
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
prisma-upgrade-v7
Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes. Use when upgrading Prisma versions, encountering v7 errors, or migrating existing projects. Triggers on "upgrade to prisma 7", "prisma 7 migration", "prisma-client generator", "driver adapter required".