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/buiphucminhtam/forgewright/token-trackernpx skills add buiphucminhtam/forgewright --skill token-trackergit clone --depth 1 https://github.com/buiphucminhtam/forgewrightWrote 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/buiphucminhtam/forgewright/token-tracker)<a href="https://agentmods.dev/skills/buiphucminhtam/forgewright/token-tracker"><img src="https://agentmods.dev/badge/skills/buiphucminhtam/forgewright/token-tracker.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 | $0.00053 | $0.04686 |
| Opus 5 | $0.00026 | $0.02343 |
| Sonnet 5 | $0.00011 | $0.00937 |
| Haiku 4.5 | $0.00005 | $0.00469 |
Grade B, and why
token-tracker 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 yesterday.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| "Permission denied" | `chmod 755 ~/.forgewright/usage` | The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 703 lines · 53 tokens per session scan B 887f96e35c46
token-tracker is a skill published in the GitHub repository buiphucminhtam/forgewright (49 stars, last pushed 2d ago), with no licence file. It adds 53 tokens to every session and 4,686 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
tokenomics-dashboard
Generate the Claude Code tokenomics dashboard for a chosen number of days of history and present it with a director-level commentary. Ask the user for one input only, the number of days of history to analyze, then state that you will fetch that data using the ccusage tool, run the analyzer, and open the resulting…
cost-tracker
Track LLM API spend per session and task. Estimate token usage across providers. Warn before you blow your budget.
security-check
Run the Cipher security-engineer persona over the repository's pending changes to catch and fix security problems before any commit or enhancement. Reviews the working diff against a catalog of real-world security anti-patterns (SSRF, injection, subprocess safety, secret/PII log leakage, weak defaults, dependency…
alert-rule-troubleshoot
This skill should be used when the user reports that an alert rule is "not firing", "no alert was sent", "the rule didn't trigger", "the rule isn't working", "it should have alerted but didn't", "why didn't I get an alert", "alert rule not firing", or wants to diagnose why a specific alert rule failed to produce an…
ops-troubleshooting
This skill should be used when the user asks to "troubleshoot", "diagnose", "debug alert", "investigate incident", "locate a fault", "investigate an alert", "diagnose a problem", "fix an issue", "check alerts", "analyze alerts", "root cause analysis", "check metrics", "check logs", or discusses…
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…