Show token usage and estimated cost per model from your local AKA store
Scanned 9/2/2026
Install to Claude Code
npx -y skills add akasecurity/ai-tc --skill tokens --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Tokens?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/akasecurity-tokens-ai-tc)More formats (shields.io, HTML) on the badges page.
---
name: aka-tokens
description: Show token usage and estimated cost per model from your local AKA store
---
# AKA tokens
Run the read script and show the user its output **exactly as printed**. The
script already prints its content inside a Markdown code fence — reproduce that
verbatim and do **not** add another code fence, strip the fence, or reformat it.
The fence is required: it is space-aligned monospace (a per-model usage table)
that Markdown would otherwise collapse. Do not reformat or summarize the table;
you may add at most one short sentence of context after it.
```bash
node "${PLUGIN_ROOT}/scripts/query.js" tokens
```
This reads the local store at `~/.aka/data/aka.db` (token counts reconciled from
your Codex CLI rollout files, grouped by provider/model, with estimated USD cost).
It is read-only. Token counts are exact; cost is **derived** at read time — a `—`
means unknown pricing (a local or non-OpenAI model/gateway), so a `≥` total is a
lower bound, not an understatement. If the store is empty, the script says so —
relay that as-is; nothing is wrong.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...