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 skills add Bilal140202/the-lord-of-the-skills --skill codeshux__tokenwisegit clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-skillsWrote 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/bilal140202/the-lord-of-the-skills/codeshux__tokenwise)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/codeshux__tokenwise"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/codeshux__tokenwise/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/bilal140202/the-lord-of-the-skills/codeshux__tokenwise"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/codeshux__tokenwise.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.00000 | $0.00661 |
| Opus 5 | $0.00000 | $0.00331 |
| Sonnet 5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
CodeShuX__tokenwise 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- summary — 91% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tokenwise:summary — Multi-session trend report
Aggregate .tokenwise/log.ndjson over a time window.
Parse $ARGUMENTS
--week(default) — last 7 days--month— last 30 days--all— entire log--days <N>— last N days--out <path>— write the report to a markdown file instead of stdout--json— output JSON instead of text
Steps
-
Read
./.tokenwise/log.ndjson(or the path the user provides) -
Filter entries to the time window:
- Compute cutoff:
now - <days>*86400 - Keep entries where
ts > cutoff
- Compute cutoff:
-
Aggregate:
- Total: sessions (unique session_id), tasks, total cost, baseline cost, savings
- Per model: task count, cost, % of total
- Per task_class: task count, avg cost, dominant model
- Trend (only for
--weekor--days <≤14>): per-day cost + savings bar chart in plain text
-
Print:
TokenWise Summary — last <N> days
==================================
Sessions: <count>
Tasks routed: <count>
Total spent: $<total>
Baseline: $<baseline>
Savings: $<savings> (<pct>%)
Per model:
Haiku <count> tasks $<cost> (<pct>%)
Sonnet <count> tasks $<cost> (<pct>%)
Opus <count> tasks $<cost> (<pct>%)
Top task classes:
<class> <count> tasks avg cost $<avg> model: <dominant>
...
Daily trend (cost):
Mon ███████░░░ $4.21
Tue ███░░░░░░░ $1.82
Wed ████████░░ $5.04
...
-
If
--out <path>was provided, write the markdown version of the report to that path. Use a proper markdown table for the trend section. -
If
--json, dump the aggregated data structure as pretty-printed JSON.
Notes on small log files
- If <2 sessions in the window: print the report but add
Note: too few sessions for meaningful trend data. - If log file is empty/missing: print the same "No TokenWise log found" message that
/tokenwise:reportuses.
Tools
Read, Bash (for jq aggregation if helpful), Write (for --out).
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.
- 12d ago First seen · 72 lines · 0 tokens per session scan A de49185354b7
CodeShuX__tokenwise is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 661 tokens. 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-31.
Other skills, from other repositories
serpsmith
Publish SEO articles reliably across AI-agent runtimes.
tool-calling-tutor
Use when a tool-calling agent does not call a tool, sends wrong arguments, loops without stopping, or needs a function schema. Guides a four-branch diagnosis and five-step schema repair. Do not use for framework-specific, MCP-server, or production-observability questions.
performing-threat-hunting-with-yara-rules
Use YARA pattern-matching rules to hunt for malware, suspicious files, and indicators of compromise across filesystems and memory dumps. Covers rule authoring, yara-python scanning, and integration with threat intel feeds.
hunt-idor
Hunting skill for idor vulnerabilities. Built from 26 public bug bounty reports. Use when hunting idor on any target.
performing-soc2-type2-audit-preparation
Automates SOC 2 Type II audit preparation including gap assessment against AICPA Trust Services Criteria (CC1-CC9), evidence collection from cloud providers and identity systems, control testing validation, remediation tracking, and continuous compliance monitoring. Covers all five TSC categories (Security…
testrail
Sync tests with TestRail. Use when user mentions "testrail", "test management", "test cases", "test run", "sync test cases", "push results to testrail", or "import from testrail".