Skip to content
cccskills
FreePublished on GitHub

economy-mode

Switch automatic model selection to lower-cost options for agent tasks, either for one session or through a saved setting. Explicit model choices remain in effect, while architecture and security review tasks use a separate economy selection.

OriginalShow the original description

Shifts Layer 3 model selection to cost-optimized alternatives when economy mode is active.

See how to install

Good for

  • Reducing costs across a session with multiple agents
  • Saving economy mode as the default setting
  • Keeping explicit model choices while changing automatic selection
  • Returning to standard model selection

Files included (1)

  • SKILL.md4.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

SCOPE

✅ THIS SKILL PRODUCES:

  • A modified Layer 3 model selection table applied when economy mode is active
  • economyMode: true written to .squad/config.json when activated persistently
  • Spawn acknowledgments with 💰 indicator when economy mode is active

❌ THIS SKILL DOES NOT PRODUCE:

  • Code, tests, or documentation
  • Cost reports or billing artifacts
  • Changes to Layer 0, Layer 1, or Layer 2 resolution (user intent always wins)

Context

Economy mode shifts Layer 3 (Task-Aware Auto-Selection) to lower-cost alternatives. It does NOT override persistent config (defaultModel, agentModelOverrides) or per-agent charter preferences — those represent explicit user intent and always take priority.

Use this skill when the user wants to reduce costs across an entire session or permanently, without manually specifying models for each agent.

Activation Methods

MethodHow
Session phrase"use economy mode", "save costs", "go cheap", "reduce costs"
Persistent config"economyMode": true in .squad/config.json
CLI flagsquad --economy

Deactivation: "turn off economy mode", "disable economy mode", or remove economyMode from config.json.

Economy Model Selection Table

When economy mode is active, Layer 3 auto-selection uses this table instead of the normal defaults:

Task OutputNormal ModeEconomy Mode
Writing code (implementation, refactoring, bug fixes)claude-sonnet-4.5gpt-5-mini
Writing prompts or agent designsclaude-sonnet-4.5gpt-5-mini
Docs, planning, triage, changelogs, mechanical opsclaude-haiku-4.5gpt-5-mini
Architecture, code review, security auditsclaude-opus-4.6claude-sonnet-4.5
Scribe / logger / mechanical file opsclaude-haiku-4.5gpt-5-mini

Prefer gpt-5-mini for all economy-mode tasks where cost is the priority.

AGENT WORKFLOW

On Session Start

  1. READ .squad/config.json
  2. CHECK for economyMode: true — if present, activate economy mode for the session
  3. STORE economy mode state in session context

On User Phrase Trigger

Session-only (no config change): "use economy mode", "save costs", "go cheap"

  1. SET economy mode active for this session
  2. ACKNOWLEDGE: ✅ Economy mode active — using cost-optimized models this session. (Layer 0 and Layer 2 preferences still apply)

Persistent: "always use economy mode", "save economy mode"

  1. WRITE economyMode: true to .squad/config.json (merge, don't overwrite other fields)
  2. ACKNOWLEDGE: ✅ Economy mode saved — cost-optimized models will be used until disabled.

On Every Agent Spawn (Economy Mode Active)

  1. CHECK Layer 0a/0b first (agentModelOverrides, defaultModel) — if set, use that. Economy mode does NOT override Layer 0.
  2. CHECK Layer 1 (session directive for a specific model) — if set, use that. Economy mode does NOT override explicit session directives.
  3. CHECK Layer 2 (charter preference) — if set, use that. Economy mode does NOT override charter preferences.
  4. APPLY economy table at Layer 3 instead of normal table.
  5. INCLUDE 💰 in spawn acknowledgment: 🔧 {Name} ({model} · 💰 economy) — {task}

On Deactivation

Trigger phrases: "turn off economy mode", "disable economy mode", "use normal models"

  1. REMOVE economyMode from .squad/config.json (if it was persisted)
  2. CLEAR session economy mode state
  3. ACKNOWLEDGE: ✅ Economy mode disabled — returning to standard model selection.

STOP

After updating economy mode state and including the 💰 indicator in spawn acknowledgments, this skill is done. Do NOT:

  • Change Layer 0, Layer 1, or Layer 2 model choices
  • Override charter-specified models
  • Generate cost reports or comparisons
  • Fall back to premium models via economy mode (economy mode never bumps UP)

Config Schema

.squad/config.json economy-related fields:

{
  "version": 1,
  "economyMode": true
}
  • economyMode — when true, Layer 3 uses the economy table. Optional; absent = economy mode off.
  • Combines with defaultModel and agentModelOverrides — Layer 0 always wins.

Anti-Patterns

  • Don't override Layer 0 in economy mode. If the user set defaultModel: "claude-opus-4.6", they want quality. Economy mode only affects Layer 3 auto-selection.
  • Don't silently apply economy mode. Always acknowledge when activated or deactivated.
  • Don't treat economy mode as permanent by default. Session phrases activate session-only; only "always" or config.json persist it.
  • Don't bump premium tasks down too far. Architecture and security reviews shift from opus to sonnet in economy mode — they do NOT go to fast/cheap models.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.

  • Locate team files across separate working directories
  • Record decisions that affect other agents
  • Request input from another specialist
github/gh-aw5.4KUpdated Oct 19, 2026

agent-conduct

FreeSummary

Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.

  • Share development rules across multiple agents
  • Keep team-specific agent names out of code and tests
  • Check affected tests before declaring work complete
github/gh-aw5.4KUpdated Oct 19, 2026

Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.

  • Designing a new workflow through questions
  • Investigating failed runs and recurring errors
  • Upgrading workflows and addressing deprecations
github/gh-aw5.4KUpdated Oct 19, 2026

Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.

  • Proposing a major architecture change
  • Replanning milestones after a foundation change
  • Comparing technical options before seeking approval
github/gh-aw5.4KUpdated Oct 19, 2026

Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.

  • Updating the firewall version used by gh-aw
  • Reviewing release notes for integration changes
  • Checking configuration schema differences
github/gh-aw5.4KUpdated Oct 19, 2026

Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.

  • Reviewing git operations after repository checkout
  • Checking tokens for private cross-repository access
  • Reviewing sparse and shallow checkout changes
github/gh-aw5.4KUpdated Oct 19, 2026

See all skills by github

Report a problem with this skill