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 antoinedc/MantaUI --skill manta-token-economygit clone --depth 1 https://github.com/antoinedc/MantaUIWrote 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/antoinedc/mantaui/manta-token-economy)<a href="https://agentmods.dev/skills/antoinedc/mantaui/manta-token-economy"><img src="https://agentmods.dev/badge/skills/antoinedc/mantaui/manta-token-economy/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/antoinedc/mantaui/manta-token-economy"><img src="https://agentmods.dev/badge/skills/antoinedc/mantaui/manta-token-economy.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.00063 | $0.00535 |
| Opus 5 | $0.00032 | $0.00267 |
| Sonnet 5 | $0.00013 | $0.00107 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
manta-token-economy 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.
What it actually says
manta-token-economy
Every turn re-reads the cached prefix. Cache reads count fully against the session quota. Task cost ≈ N_turns × (initial_prefix + cumulative additions).
Discipline:
-
Batch independent tool calls in one turn. Issue multiple
Read/Grep/Bashin parallel within a single message, not back-to-back turns. One turn ≫ three turns. -
Compound shell commands.
cmd1 && cmd2 && cmd3(or;for non-dependent) for multi-step inspection — never sequential single-command bash turns. -
Don't re-Read after Edit.
Editvalidatesold_string; trust the prior Read. Re-reading the same file adds thousands of tokens to every subsequent turn's cache_read. -
Use
offset/limiton large Reads. A 36KB file is ~9k tokens × every later turn. Read only the relevant section. -
No
--output json | head/ huge JSON dumps from bash. Use--output tablefor inspection; project specific fields with--jq/python3 -cwhen JSON is needed. -
Compound
gitops.git status && git diff --stat && git log -3in one bash call, not three turns. -
Prefer
GrepoverBashfor content search. Don't rungreporrgvia Bash when theGreptool exists — it's faster and returns structured results without parsing overhead. -
Batch file reads when inspecting a directory. If you need to understand the structure of
src/main/,src/renderer/, etc., read the directory listing once and use it to plan targetedReads — don't read files one at a time in separate turns. -
Avoid redundant verification turns. If you just ran
npm run typecheck && npm testand both passed, don't run them again to "confirm" before posting results. Trust the output you just captured.
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 · 47 lines · 63 tokens per session scan A 13171778cb01
manta-token-economy is a skill published in the GitHub repository antoinedc/MantaUI (12 stars, last pushed 6d ago), licensed MIT. It adds 63 tokens to every session and 535 once invoked, about $0.0003 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-31.
Other skills, from other repositories
im-adapter
Format responses for instant messaging platforms such as Lark, DingTalk, WeCom, Slack, and Telegram. Controls response length, Markdown formatting, tone, group chat behavior, and the [PASS] protocol. Also covers sending images and files via [SENDIMAGE]/[SENDFILE] markers on channels that support media (currently WeCom…
message-push
Send proactive messages to IM groups or individual users via the gateway Send API. Use when the user says to send, post, notify, forward, or tell someone a message on Feishu, Slack, Telegram, Discord, DingTalk, or WeCom.
general
Handle everyday conversation, answer questions, manage files, take notes, run scripts, and maintain persistent memory across sessions. Use when the user asks a general question, requests file operations, wants to brainstorm ideas, needs to-do tracking, asks you to remember something, or requests skill search and…
multi-bot
Coordinates responses between multiple GolemBot instances in a shared fleet. Use when the bot operates in a group chat with other bots, needs to decide whether to respond or pass, or must call a peer bot's API to fetch cross-domain data.
data-analysis
Loads CSV, Excel, and JSON data files, performs statistical analysis, and generates charts and reports. Use when the user asks to analyze a dataset, compute statistics, create visualizations, find trends, or produce a data report.
kb-guide
Search, read, create, and update knowledge base entries via MCP-connected KB tools. Use when the user asks to look up documentation, find existing articles, check if docs exist on a topic, create a new KB entry, update an existing document, or when domain questions should be answered from the knowledge base first.