Claude Code CLI

executing-claude

Purpose

Use this skill to perform coding, research, or automation tasks using the claude CLI. It maps requests to Claude's native permission modes to balance automation with security.

Permission Tiers

Implementation Workflow

1. Budget Verification (Optional but Recommended)

Before initiating complex or long-running tasks, verify the remaining token/cost budget to avoid suspension.

• Tools: Use ccusage daily --json to check current consumption.
• Constraints: If the daily cost is approaching the limit, alert the user or use the --max-budget-usd flag for the session.

2. Analyze & Classify

Analyze the user's intent to determine the required permission tier.

• Tier 0 (Plan): Does the task only involve reading code or searching for information?
• Tier 1 (Accept Edits): Does the task involve modifying files but no command execution?
• Tier 1.5 (Auto): Is the task long-running and would interactive prompting be disruptive? Does the user have a Team/Enterprise plan and use Sonnet 4.6 or Opus 4.6? If yes, prefer auto over bypassPermissions — the classifier will block risky operations automatically.
• Tier 2 (Bypass Permissions): Does the task require running tests, build scripts, or managing dependencies autonomously, and auto mode is unavailable or insufficient?

2. Approval Protocol

If the task maps to Tier 1 or Tier 2, you MUST obtain user approval before executing the claude command.

Use the AskQuestion tool to confirm:

"I've detected that this task requires [Accept Edits/Bypass Permissions] permissions to [modify files/run shell commands]. OK to proceed?"

3. Execution

Execute claude using the mode determined by the tier. Use --max-budget-usd for non-interactive tasks where cost control is critical.

# Tier 0 (Plan + sandbox — read-only, OS-level isolation, shell blocked)
claude -p "<prompt>" --permission-mode plan --sandbox \
  --disallowedTools Bash --max-budget-usd 1.0

# Tier 1 (Accept Edits + sandbox — file writes allowed, shell gated, OS-level isolation)
claude -p "<prompt>" --permission-mode acceptEdits --sandbox

# Tier 1.5 (Auto — all actions; background classifier blocks risky operations)
# Requires Team/Enterprise/API plan and Sonnet 4.6 or Opus 4.6
claude -p "<prompt>" --permission-mode auto

# Tier 2 (Bypass Permissions — sandbox omitted; must run shell commands freely)
claude -p "<prompt>" --permission-mode bypassPermissions

Security Rules:

• ALWAYS pass --sandbox for Tier 0 and Tier 1. Skip only when OS prerequisites are unavailable (Linux requires bubblewrap + socat: sudo apt-get install bubblewrap socat; macOS uses built-in Seatbelt).
• For Tier 0, also pass --disallowedTools Bash to block shell execution at the tool layer.
• NEVER use --permission-mode bypassPermissions without explicit confirmation of the risks.
• ALWAYS use the most restrictive mode possible (prefer plan).
• If you are unsure, default to plan and escalate only if claude reports it cannot complete the task.
• Prefer auto over bypassPermissions when eligibility conditions are met — the classifier provides safety guardrails without requiring manual approval for every action.
• auto mode classifier behavior: The classifier runs on Sonnet 4.6 regardless of the main session model, and its calls count toward token usage. Extra cost is incurred mainly by shell commands and network operations; read-only actions and local file edits do not trigger classifier calls. If the classifier blocks an action, claude pauses and asks the user before proceeding.
• auto mode is not available on Haiku or claude-3 models. If using these models, fall back to Tier 1 (acceptEdits) or Tier 2 (bypassPermissions) as appropriate.
• --permission-mode bypassPermissions vs --dangerously-skip-permissions: bypassPermissions still respects explicit deny rules in settings.json. The --dangerously-skip-permissions flag bypasses ALL checks including the deny list — never use it outside a fully isolated container.

What the auto classifier blocks by default:

• Downloading and executing code (curl | bash, scripts from cloned repos)
• Sending sensitive data to external endpoints
• Production deploys and migrations
• Mass deletion on cloud storage
• Granting IAM or repo permissions
• Modifying shared infrastructure
• Destructively destroying files that existed before the session started
• Force-pushing or pushing directly to main

What the auto classifier allows by default:

• Local file operations in the working directory
• Installing dependencies from lock files
• Reading .env and sending credentials to matching APIs
• Read-only HTTP requests
• Pushing to the branch you started on or one claude created

Configuration

This skill leverages native claude CLI flags to enforce the permission tiers.

Model Selection

The default model depends on your Claude plan:

Override at invocation time with --model <shorthand-or-id>, or change mid-session with /model <shorthand>:

claude --model sonnet -p "<prompt>" --permission-mode plan
claude --model opus   -p "<prompt>" --permission-mode acceptEdits

Available model IDs: claude-opus-4-6, claude-sonnet-4-6, claude-haiku-4-5.

Cloud Agent Handoff

Claude Code offers two remote execution modes beyond local CLI.

Cloud Execution (research preview — Pro / Max / Team / Enterprise)

Tasks run on Anthropic-managed VMs with pre-installed runtimes. Code is cloned to an isolated container; no local machine required.

# Kick off a cloud task
claude --remote "<task>"

# Monitor all running cloud tasks (in any interactive session)
/tasks

Security note: Cloud tasks run with --dangerously-skip-permissions by default. Only committed repo hooks and a setup.sh script apply; user-level settings.json is ignored. Use for well-defined, async tasks where local oversight is not required.

Remote Control (GA — Feb 2026)

Code stays on your local machine. Remote Control synchronizes access so you can monitor and steer the same agent session from another device (phone, tablet, web at claude.ai/code).

# Pull a web or mobile session back to your terminal
claude --teleport
claude --teleport <session-id>

Examples

Refer to references/usage-examples.md for concrete scenarios.