modes-authoring
Guide to writing ai-cli mode files. Use when creating modes for non-interactive Claude Code sessions — preconfigured agent runs with locked-in system prompts, model selection, and prompt wrappers.
What this skill does
# Writing ai-cli Modes
Modes are markdown files that configure non-interactive Claude Code sessions via the Agent SDK. Each mode defines a system prompt, model, and optional prompt wrapper — producing a preconfigured, fire-and-forget agent.
## File Location
| Location | Scope | Precedence |
|----------|-------|------------|
| `.claude/.ai/modes/<name>.md` | Project-local | Wins over built-in |
| `ai-cli/modes/<name>.md` | Built-in (bundled) | Fallback |
## Required Frontmatter
```yaml
---
model: opus
system-prompt-mode: append
---
```
| Field | Required | Values | Default |
|-------|----------|--------|---------|
| `model` | Yes | Any valid model ID | — |
| `system-prompt-mode` | No | `append`, `replace` | `append` |
- **`append`** — mode's system prompt is appended to the default Claude Code system prompt. The agent retains all standard capabilities.
- **`replace`** — mode's system prompt completely replaces the default. Use for fully custom agent personas.
## Body: System Prompt
Everything after the frontmatter (before `## Prompt Wrapper` if present) becomes the system prompt content.
```markdown
---
model: claude-sonnet-4-5-20250929
system-prompt-mode: append
---
You are a security auditor. Report vulnerabilities only — never edit code.
Focus on: injection, auth bypass, data exposure, SSRF.
```
## Prompt Wrapper (Optional)
A `## Prompt Wrapper` heading defines a template applied to the user's `-p` argument. Use `{{prompt}}` as the placeholder.
```markdown
---
model: opus
system-prompt-mode: append
---
You are a systematic debugger. Investigate only — no code changes.
## Prompt Wrapper
Debug the following issue. Diagnose root cause — don't fix.
Issue description:
{{prompt}}
```
Without a prompt wrapper, the `-p` argument is passed directly as the user prompt.
## Usage
```bash
# Built-in mode
ai -m review -p "src/auth/"
# Project-local mode
ai -m security-audit -p "check the API layer"
# List all available modes (built-in + local)
ai -l
```
## Design Principles
1. **Constraints over procedures** — tell the agent what to focus on and what not to do, not step-by-step instructions
2. **Pick the right model** — haiku/sonnet for cheap triage, opus for deep analysis
3. **`append` for most modes** — the agent keeps Claude Code's full toolset; you're just narrowing its focus
4. **`replace` sparingly** — only when you need a completely custom persona
5. **Prompt wrappers for structure** — frame the user's input when the mode expects a specific format
## Examples: Built-in Modes
- **`general`** — sonnet, append, no wrapper. Minimal: "direct, efficient assistant"
- **`debug`** — opus, append, wrapper frames input as "Issue description". Multi-phase methodology in system prompt.
- **`review`** — opus, append, wrapper frames input as review target. Detailed concern taxonomy in system prompt.
## Composability
Modes are callable from hooks, scripts, and other tools:
```bash
# In a pre-commit hook
ai -m validate-commit -p "$(git diff --cached)"
# In a CI script
ai -m review -p "$(git diff origin/main...HEAD)"
```
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.