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.
git clone --depth 1 https://github.com/gatalifeltd/economizer-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/rules/gatalifeltd/economizer-skills/token-economy)<a href="https://agentmods.dev/rules/gatalifeltd/economizer-skills/token-economy"><img src="https://agentmods.dev/badge/rules/gatalifeltd/economizer-skills/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/rules/gatalifeltd/economizer-skills/token-economy"><img src="https://agentmods.dev/badge/rules/gatalifeltd/economizer-skills/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.00291 | $0.00291 |
| Opus 5.5 | $0.00116 | $0.00116 |
| Sonnet 5.5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
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 6d 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
Token economy rules
- Trim tool outputs to the few fields that matter — never echo full logs or files back.
- Answer terse and structured, with hard caps — ≤ N items, one sentence each, diff-only.
- Don't restate context or quote large blocks back — reference by path/line, don't reproduce.
- Batch independent calls into one message — reads, searches and checks that don't depend on each other go out together; one call per turn only when the next step needs the result.
- Read by range, not whole files —
grep -nfirst, then only the needed lines; a whole file only when the task needs all of it; don't re-read an unchanged file. - One small screenshot per check — scaled or zoomed for your own checks; full size only for QA evidence a human reviews.
- Send wide exploration to a subagent — when finding the answer means reading more than ~50k tokens, let a subagent read and return only the conclusion; open the cited lines before acting on it.
Rules 4-7 shrink the context that every later call re-reads from cache.
For trivial one-liners, use judgment — brevity shouldn't cost correctness.
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.
- 6d ago Changed · +6 lines · +175 tokens per session bb886103448c
- 2mo ago First seen · 14 lines · 116 tokens per session scan A 7d40e7c8de0e
token-economy is a cursor rule published in the GitHub repository gatalifeltd/economizer-skills (3 stars, last pushed 7d ago), licensed MIT. It adds 291 tokens to every session, about $0.0012 per session on Opus 5.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 cursor rules, from other repositories
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
feedback-enhanced
Rules for an interactive feedback system that lets users and an AI agent discuss complex development work in real time. It includes guidance for recording decisions, tracking progress and handling detailed inputs such as code and diagrams.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
122-swift-development
122: Swift development workflow including TDD, refactoring, and performance optimization.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.