Cost Efficiency logo

Cost Efficiency

Community
cubetribe
cost-efficiency

Smart Routing — the DEFAULT CC_GodMode routing policy. Risk-based, minimal-agent paths that preserve required safety gates for the changed scope.

Overview

Publishercubetribe
RepositoryClaudeCode_GodMode-On
Skill namecost-efficiency
Stars
54
Forks
10
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by cubetribe on GitHub. Read the source before you install it.

Installation

Install the Cost Efficiency AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/cubetribe/ClaudeCode_GodMode-On/tree/main/skills/cost-efficiency
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/cubetribe/ClaudeCode_GodMode-On.git /tmp/ClaudeCode_GodMode-On
mkdir -p .claude/skills
cp -r /tmp/ClaudeCode_GodMode-On/skills/cost-efficiency .claude/skills/cost-efficiency
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cost Efficiency in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cost Efficiency on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cost Efficiency is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Smart Routing (Default Routing Policy)

This is the default routing mode. The Orchestrator applies Smart Routing automatically unless the task carries high-risk signals that require Full-Gates (see skills/workflows/).

Smart Routing changes routing behavior. It does not silently weaken security, contract, or release gates.

Core Principle

Spend strong reasoning only where it changes the outcome.

Everything else should be:

  • batched
  • bounded
  • summarized
  • delegated only when it saves more context than it costs
  • validated against the changed scope instead of the whole repository

Architecture Gate (Split)

For small/medium tasks (no new modules, no breaking changes, no cross-domain design):

  • Orchestrator writes a 3–5 bullet inline architecture brief directly into reports/vX.Y.Z/sprint-NN/01-architect-report.md.
  • No @architect subagent invocation needed.
  • The brief's 3–5 bullets MUST cover all five required fields (see below). A brief missing any field is invalid — invoke @architect instead of proceeding on an underspecified design.

For high-risk tasks (new modules, breaking changes, cross-domain design, uncertain scope):

  • Invoke @architect (Opus) via Task tool as normal.
  • Full-Gates path applies.

Inline Architecture Brief — Required Fields

The brief stays 3–5 bullets (cost-efficiency spirit unchanged) — these are the fields those bullets must cover, not additional sections:

  1. Decision — the design/approach actually taken.
  2. Rejected alternative — at least one alternative considered and why it lost.
  3. Constraints — what binds the implementation (technical, contractual, scope).
  4. Out-of-scope — explicitly what this brief does NOT cover.
  5. Affected contracts/APIs — named, or "none".

Missing any of the five ⇒ the brief is invalid; escalate to @architect rather than handing @builder an underspecified design. See docs/templates/REPORT_TEMPLATES.md for the exact inline-brief report variant (frontmatter, field labels).

Default Routing

Work typeSmart Routing route
Docs-only@scribe only; no @builder unless files need structural edits
Simple bug@builder -> deterministic hook; @tester only if ux_gate: auto
Unknown facts@researcher with strict source/time budget
Small/medium featureinline arch brief + @builder + deterministic hook + @tester/@security/code-review as declared/applicable
Architecture risk@architect, but with a narrow decision brief
API or schema risk@api-guardian remains mandatory
UI behavior@tester only on affected flows and viewports
Release or PR@github-manager only after @scribe produces final notes

Escalate to Full-Gates When

Any of these risk signals force the Full-Gates path (skills/workflows/):

  • API/schema/type paths touched — the canonical path list lives in skills/api-change/ and nowhere else
  • Security surfaces (.github/workflows/, auth code, secrets handling)
  • Release artifacts (VERSION, CHANGELOG.md)
  • User-facing UI changes
  • New modules or cross-domain designs
  • Breaking changes

Routing Log (Mandatory)

Every Smart Routing decision and every agent skip is logged before dispatch — no exceptions. See docs/templates/SPRINT_TEMPLATE.md § Routing Log for the exact format string and example — that section is the single canonical definition; this skill does not duplicate it.

Planned work logs this in the sprint file's ## Routing Log section; implicit sprint-00 work logs the same line in the report header instead.

Why this exists: a misrouted task bypasses every downstream gate invisibly — Smart Routing's whole value is skipping agents when the risk profile allows it, but an unlogged skip means nobody can tell, after the fact, whether that call was justified or a silent gap. The log turns each minimal-path decision into a post-hoc auditable, re-examinable record instead of an invisible judgment call. A gate-skip without a matching log line is a contract violation — reviewers (the deterministic hook, @tester/@security when they run, the Orchestrator on re-check) return BLOCKED (quality).

Research Budget

When @researcher is needed:

  • define the exact question first
  • prefer official and primary sources
  • cap source collection to the smallest useful set
  • return only facts, source links, and routing implications
  • do not perform broad background research unless the user asks

Agent Budget

  • Avoid Agent Teams unless the user explicitly accepts the cost.
  • Avoid Departments Mode unless ownership is genuinely unclear.
  • Keep active subagents to the smallest useful set.
  • Reuse existing reports and state only after checking they are current.
  • Ask agents for concise structured reports, not full transcripts.

Model Budget

Use existing agent model assignments as the baseline:

  • @researcher and @github-manager are already low-cost lanes.
  • @architect should be reserved for decisions with long-lived impact.
  • @builder and @tester stay on balanced models because bad implementation or weak validation often costs more than the saved tokens.
  • @scribe is on haiku — templated doc work is sufficient.

effort frontmatter fields (Claude Code ≥2.1.152) provide additional budget tuning per agent without model changes.

If the user asks for an explicit model downgrade beyond defaults, state the risk and get approval before changing agent definitions or runtime config.

Validation Budget

Run checks that match the changed scope:

  • changed Markdown or prompts: syntax, link/path sanity, manifest references
  • changed scripts: node --check or bash -n, plus targeted smoke
  • changed hooks: event payload assumptions and a dry-run where possible
  • changed API/contracts: @api-guardian plus consumer checks
  • changed UI: affected flows only unless release risk is high

Precedence vs. Parallel-First

Smart Routing decides which agents run (smallest useful set). CLAUDE.md's parallel-first doctrine decides how independent units are scheduled (fan-out with disjoint write scopes). They compose: pick the minimal set first, then parallelize only genuinely independent units. Smart Routing never skips required gates, and parallel fan-out never overrides ownership rules.


CC_GodMode — © 2025–2026 Dennis Westermann (dennis-westermann.de). Proprietary — not open source. Free for private, non-commercial use; redistribution or re-hosting outside GitHub is prohibited; attribution required. Official source: github.com/cubetribe/ClaudeCode_GodMode-On. See LICENSE.

Frequently asked questions

What does the Cost Efficiency AI skill do?

Smart Routing — the DEFAULT CC_GodMode routing policy. Risk-based, minimal-agent paths that preserve required safety gates for the changed scope.

Why use Cost Efficiency on TypingMind?

Because you install it once and use it with any model. Cost Efficiency is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cost Efficiency in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cubetribe/ClaudeCode_GodMode-On/tree/main/skills/cost-efficiency. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Cost Efficiency?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cost Efficiency?

As many as you like. As long as a model supports skills, you can use Cost Efficiency with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cost Efficiency AI skill free?

It is published on GitHub by cubetribe. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇