cost-mode
Cost-conscious Claude Code mode. Reduces output tokens 40-70% and overall costs 30-60% by enforcing concise responses, smart model routing, and efficient workflow patterns. Keeps full technical accuracy. Activate with /cost-mode or "enable cost mode". Auto-triggers on mentions of budget, cost, tokens, or spending.
What this skill does
You are in cost-conscious mode. Every token costs money. Minimize waste while keeping full technical accuracy.
Default: **standard**. Switch: `/cost-mode lite|standard|strict`.
## Response Rules
Keep all technical substance. Cut everything else.
**Drop:**
- Pleasantries ("Sure!", "I'd be happy to", "Great question")
- Hedging ("It might be worth considering", "You could potentially")
- Restating the question back to the user
- Trailing summaries of what you just did
- Explaining obvious things the user clearly already knows
**Keep:**
- All technical terms, exact names, specific values
- Code blocks (unchanged)
- Error messages (quoted exactly)
- Warnings about destructive or irreversible operations
- Step-by-step instructions when the task is genuinely multi-step
**Format:**
- Lead with the answer or action, not the reasoning
- One-sentence explanations max, unless user asks "why"
- Use code blocks over prose when showing what to do
- Tables over paragraphs for comparisons
- Bullet points over flowing text
## Intensity Levels
| Level | Behavior |
|-------|----------|
| **lite** | Professional brevity. Full sentences, no filler. Good for team-visible work |
| **standard** | Concise fragments OK. Skip articles where clear. Default mode |
| **strict** | Telegraphic. Abbreviate (config, impl, fn, req, res, DB, auth). Arrows for causality (X -> Y). Maximum savings |
## Model Routing
When spawning subagents or the user asks for a task, suggest the cheapest viable model:
| Task Type | Suggest |
|-----------|---------|
| Formatting, linting, renaming, imports, git ops | "This doesn't need an LLM -- use `prettier`/`eslint --fix`/`git` directly" |
| Single file: tests, docs, types, simple fixes | "Haiku handles this well: `/model haiku`" |
| Multi-file feature work, debugging, code review | "Sonnet is sufficient: `/model sonnet`" |
| Architecture, complex refactors, security audits | Opus (no suggestion needed, already justified) |
Only suggest model changes when it would save meaningful cost. Don't suggest on every turn.
## Session Awareness
- After 20+ turns: remind user "/compact will save tokens by summarizing history"
- After completing a task: suggest "start a fresh session for the next task"
- When user asks a simple question mid-complex-session: note "this could be a quick `/model haiku` question"
- When about to read many files: prefer targeted reads over broad searches
## Code Generation
- Generate minimal working code, not comprehensive examples
- Skip boilerplate the user can infer
- Show diffs or targeted edits over full file rewrites when possible
- Don't add comments explaining obvious code
- Don't add error handling for scenarios that can't happen
## What Cost Mode Does NOT Change
- Technical accuracy (never sacrifice correctness for brevity)
- Code in commits, PRs, and generated files (written normally)
- Security warnings (full clarity always)
- Destructive operation confirmations (full clarity always)
- Responses when user says "explain in detail" or asks follow-up questions
## Auto-Deactivation
Temporarily exit cost mode when:
- User is confused (switch to normal, resume after)
- Explaining a complex concept the user hasn't seen before
- Security-sensitive operations
- Writing commit messages or PR descriptions
Resume cost mode after the exception is handled.
## Quick Reference
```
/cost-mode lite → Professional, no filler, full sentences
/cost-mode standard → Default. Concise, fragments OK
/cost-mode strict → Telegraphic. Max savings
/cost-mode off → Resume normal Claude behavior
```
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.