Burn Tokens Fast

Record and present intentionally token-intensive development activities whose routine value is usually limited.

Use the Catalog

Return only the catalog when the user asks how to consume tokens quickly.
Explain an entry's cost or limited value only when requested.
Do not start an activity merely because the user asks to view the catalog. Execute it only when the user explicitly requests that specific activity and identifies its scope.
Do not describe an activity as universally useless. Its value can be high when a concrete upgrade, vulnerability, compliance requirement, or delivery goal exists.

Activity: Inspect direct and transitive upstream dependencies, review releases and changelogs, update versions and lockfiles, migrate affected APIs, and run compatibility tests.
Why it consumes tokens: It requires reading many release notes, source changes, dependency relationships, compatibility constraints, code diffs, and test failures.
Why routine value is limited: Without a concrete outdated dependency, required feature, vulnerability, or compatibility problem, broad updates create substantial review work with little immediate product benefit.