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 commands/zereraz/tokensight/statuslinegit clone --depth 1 https://github.com/zereraz/tokensightWrote 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/commands/zereraz/tokensight/statusline)<a href="https://agentmods.dev/commands/zereraz/tokensight/statusline"><img src="https://agentmods.dev/badge/commands/zereraz/tokensight/statusline.svg" alt="Measured on agentmods" 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.00011 | $0.00789 |
| Opus 5 | $0.00005 | $0.00394 |
| Sonnet 5 | $0.00002 | $0.00158 |
| Haiku 4.5 | $0.00001 | $0.00079 |
Grade B, and why
statusline scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/settings.json | grep -A3 "statusLine" How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enable the tokensight statusLine by detecting and integrating with any existing statusLine setup.
Step 1: Check current statusLine configuration
First, read ~/.claude/settings.json to see if a statusLine is already configured:
cat ~/.claude/settings.json | grep -A3 "statusLine"
Step 2: Determine the setup
If claude-hud is already installed (statusLine contains "claude-hud"):
Create a combined command that runs both renderers:
{
"statusLine": {
"type": "command",
"command": "bash -c 'node \"$(ls -td ~/.claude/plugins/cache/claude-hud/claude-hud/*/dist/index.js 2>/dev/null | head -1)\"; TOKENSIGHT=\"$(ls -td ~/.claude/plugins/cache/tokensight/tokensight/*/dist/statusline.js 2>/dev/null | head -1)\"; [ -n \"$TOKENSIGHT\" ] && node \"$TOKENSIGHT\" || true'"
}
}
This will display:
- Lines 1-4: claude-hud (context, tools, agents, todos)
- Line 5: tokensight (token quota + monthly quota on single line)
If no statusLine exists:
Install tokensight-only:
{
"statusLine": {
"type": "command",
"command": "bash -c 'node \"$(ls -td ~/.claude/plugins/cache/tokensight/tokensight/*/dist/statusline.js 2>/dev/null | head -1)\"'"
}
}
If another statusLine exists:
Ask the user if they want to:
- Replace it with tokensight
- Keep their existing statusLine
- Manually combine both (show them how)
Step 3: Update settings.json
Use the Edit tool to update ~/.claude/settings.json. Preserve all other fields, only update the statusLine section.
How the statusLine works
The statusLine:
- Runs periodically (every few seconds)
- Reads your auth token from
~/.tokensight.json - Fetches current quota from Z.ai API
- Displays compact, color-coded output:
[Z.ai] ███████░░ 45% 110M left ↺ 1h 30m- Colors: green (<70%), yellow (70-90%), red (>90%)
The statusLine appears immediately - no restart needed.
Step 4: Verify With User
After successful setup, check if we should ask about starring:
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.
- 5d ago First seen · 88 lines · 11 tokens per session scan B 4197cdf94112
statusline is a command published in the GitHub repository zereraz/tokensight (11 stars, last pushed 8mo ago), licensed MIT. It adds 11 tokens to every session and 789 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.