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/hunter-io/claude-plugin/check-usagenpx skills add hunter-io/claude-plugin --skill check-usagegit clone --depth 1 https://github.com/hunter-io/claude-pluginWhat 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.00043 | $0.00413 |
| Opus 5 | $0.00022 | $0.00206 |
| Sonnet 5 | $0.00009 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
check-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 3d 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.
What it actually says
Check Usage
Read-only view of the account's plan, credits, and usage. No credits consumed, no changes made.
Examples
/hunter:check-usage How many credits do I have left?"What plan am I on?""How many searches have I used this month?""Show my account details"
Steps
-
Read the account →
Get-Account-Detailsfor plan and reset date;Get-Usagefor search/verification consumption and what's remaining. Neither tool returns a team name — don't show one. -
Present a clear summary — show what's REMAINING, not the allowance. Use
requests.credits.remainingwhen the account has a single credits bucket; otherwise computeavailable - usedper bucket. (availableis the period allowance plus packs, not what's left.)
# Account Usage
| | Used | Remaining | Resets |
|--|------|-----------|--------|
| **Searches** | 320 | 180 | 2026-08-01 |
| **Verifications** | 140 | 860 | 2026-08-01 |
**Plan:** Starter
- If the user is close to a limit, flag it: "You've used 90% of your monthly searches — they reset on [date]."
Credit Cost
Free — reading account details and usage consumes no credits.
Important Notes
- Read-only. This skill never creates API keys, changes the plan, or edits account settings — those stay in the Hunter dashboard.
- Handy as a pre-check before running bulk verification or enrichment.
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.
- 3d ago First seen · 46 lines · 43 tokens per session scan A 93f257482c98
check-usage is a skill published in the GitHub repository hunter-io/claude-plugin (9 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 413 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…