Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ww-w-ai/super-token-saver/plugin install super-token-saverWrote 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/skills/ww-w-ai/super-token-saver/report-limit)<a href="https://agentmods.dev/skills/ww-w-ai/super-token-saver/report-limit"><img src="https://agentmods.dev/badge/skills/ww-w-ai/super-token-saver/report-limit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ww-w-ai/super-token-saver/report-limit"><img src="https://agentmods.dev/badge/skills/ww-w-ai/super-token-saver/report-limit.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.01458 |
| Opus 5 | $0.00014 | $0.00729 |
| Sonnet 5 | $0.00006 | $0.00292 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
report-limit 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 4d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code only today. Codex reports its rate limits directly (
rate_limits.primary.used_percent,resets_at), so this is a port that has not been done yet, not a limitation — seedocs/CODEX-PORT-BACKLOG.md.
Report rate-limited 5-hour windows to GitHub Discussions. Pure rule-based — no LLM reasoning needed.
Help
ONLY show help if the user's argument literally contains the word "help" (e.g. /report-limit help). If no argument or any other argument is given, SKIP this section entirely and proceed to execution.
If the user provides "help" as argument, show usage summary and stop:
/report-limit — Report your rate limit data
Got rate limited? This skill automatically finds your blocked
5-hour windows from cached timeline data and opens a pre-filled
GitHub Discussion to ww-w-ai/super-token-saver.
No manual input needed. Just run it and confirm in your browser.
Options:
(nothing) Auto-detect and report all rate-limited windows
<date> Report a specific date (e.g. /report-limit 2026-04-01)
help Show this help
Examples:
/report-limit Report all rate-limited windows
/report-limit 2026-04-01 Report all 5h windows on April 1st
Do not run any analysis. Just display the help text and stop.
Execution
Before running, ask the user's plan if not already known. The prompt message MUST be in the user's language (detect from conversation context). The table content (Plan names, prices) stays in English since they are proper nouns.
Select your current Claude plan. The report will be generated based on your plan type.
(Translate the above message naturally into the user's language.)
# Plan Price 1 Pro $20/mo 2 Max 5x $100/mo 3 Max 20x $200/mo 4 Team Standard $20/seat/mo 5 Team Premium $100/seat/mo 6 Enterprise custom 7 Amazon Bedrock usage-based 8 Microsoft Foundry usage-based 9 Google Vertex AI usage-based Enter number or name (e.g. "3" or "max200"):
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.
- 4d ago Changed · +1 tokens per session f94fd7cfb704
- 12d ago First seen · 116 lines · 27 tokens per session scan A bd24c08a1d3d
report-limit is a skill published in the GitHub repository ww-w-ai/super-token-saver (31 stars, last pushed 4d ago), licensed Apache-2.0. It adds 28 tokens to every session and 1,458 once invoked, about $0.0001 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
cco-budget
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — Claude 5 lineup, Opus 5 default fallback, full 1M context at standard price).
cco-config
View and tune CCO's behavior thresholds — re-read warnings, cache staleness, prompt-coach length bands, and the /cco-pack budget cap.
cco-patterns
Share learned file patterns across a team — export an anonymized digest of what's usually waste/useful/co-edited, and import a teammate's so a fresh clone benefits day one.
cco-tools
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses.
cco-clean
Clean up old tracking data and reset statistics.
agent-harness-optimizer
Use when agent harness optimization patterns for token efficiency, memory persistence, session management, and cross-harness parity. Use when optimizing agent performance, reducing token costs,.