token-economy

Audit AI agent sessions for redundant token consumption against FR-26 rules.

6|Updated May 29, 2026
One-click install
npx skills add https://github.com/fusebase-dev/fusebase-flow --skill token-economy-fusebase-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token-economy
Source: https://github.com/fusebase-dev/fusebase-flow/tree/main/flow-skills/token-economy
Command: npx skills add https://github.com/fusebase-dev/fusebase-flow --skill token-economy-fusebase-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses redundant token consumption during AI agent work sessions that drives up operational costs and reduces efficiency without delivering value, while ensuring quality and correctness are never sacrificed in the process.

Core Features & Use Cases

  • FR-26 Rule Enforcement: Implements core execution-time economy rules including scoped reads, no re-reads of unchanged in-context files, two-strike retry rule, and targeted edits, each paired with quality guards to prevent correctness compromises.
  • Token Waste Auditing: Provides a path to run /token-waste-audit on Claude Code or use repo-side fallback metrics on other surfaces to identify redundant consumption candidates mapped to FR-26 rules.
  • Context Compression Discipline: Extends economy rules to large inputs and outputs with guidelines for routing, extracting, and preserving retrieval paths for large artifacts to avoid unnecessary context loading.
  • Use Case: Use this Skill when debugging long tool-using AI development sessions, responding to user questions about high session costs or token waste, or running formal token waste audits for your AI workflow.

Quick Start

Invoke the token-economy skill when you need to audit your last AI development session for redundant token usage and receive a report of potential waste candidates aligned with FR-26 economy rules.

Frequently Asked Questions about token-economy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce token waste in long AI development sessions?

Token waste in long AI sessions is reduced by enforcing FR-26 economy rules like scoped reads, avoiding re-reads of unchanged files, and applying context compression discipline for large inputs and outputs.

What is a token waste audit and how does it work?

A token waste audit identifies redundant token consumption in AI agent sessions by mapping waste candidates to FR-26 economy rules using deterministic stdlib-only tooling across Claude Code, Codex, Cursor, Copilot, and Gemini.

How do I enforce context compression for large artifacts in AI workflows?

Context compression for large artifacts is enforced by routing, extracting, and preserving retrieval paths, which avoids loading unnecessary context into the AI session and reduces operational costs.

Does the token economy skill work with Cursor and Copilot?

Yes, token economy enforcement works across Claude Code, Codex, Cursor, Copilot, and Gemini, using the /token-waste-audit command on Claude Code or repo-side fallback metrics on other development surfaces.

How can I stop AI agents from re-reading unchanged files and wasting tokens?

AI agents stop re-reading unchanged files by applying FR-26 execution-time economy rules, which include scoped reads, a two-strike retry rule, and targeted edits paired with quality guards to prevent correctness compromises.

When should I run a token waste audit on my AI development workflow?

You should run a token waste audit when debugging long tool-using AI development sessions, investigating high session costs, or enforcing context compression discipline for large inputs and outputs.