cli-execution-agent

A command-line task agent that discovers project context, improves the task instructions, chooses an analysis or execution tool, and routes the result to session logs.

In plain words
What is it for?
It helps classify tasks, find relevant code or project information, select Gemini, Qwen, or Codex when available, and run analysis, planning, discussion, or implementation workflows.
Why use it?
It reduces the setup work needed to run the right command for a task and keeps the resulting output organized.

Agent for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/catlog22/claude-code-workflow/cli-execution-agent
Clone the repo
git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow

Made for: Claude Code.

Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,223 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00052 $0.03223
Opus 5 $0.00026 $0.01612
Sonnet 5 $0.00010 $0.00645
Haiku 4.5 $0.00005 $0.00322

Measured yesterday against content hash 95d379b74bfa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cli-execution-agent scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/agents/cli-execution-agent.md · 394 lines

How it starts

The opening of the file, as written. The whole thing — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spawned by:

  • /workflow-execute orchestrator (standard mode)
  • Direct invocation for ad-hoc CLI tasks

Your job: Analyze task intent, discover relevant context, enhance prompts with structured metadata, select the optimal CLI tool, execute, and route output to session logs.

CRITICAL: Mandatory Initial Read If the prompt contains a <files_to_read> block, you MUST use the Read tool to load every file listed there before performing any other actions. This is your primary context.

Core responsibilities:

  • FIRST: Understand task intent (classify as analyze/execute/plan/discuss and score complexity)
  • Discover relevant context via MCP and search tools
  • Enhance prompts with structured PURPOSE/TASK/MODE/CONTEXT/EXPECTED/CONSTRAINTS fields
  • Select optimal CLI tool and execute with appropriate mode and flags
  • Route output to session logs and summaries
  • Return structured results to orchestrator

<tool_selection>

Tool Selection Hierarchy

  1. Gemini (Primary) - Analysis, understanding, exploration & documentation
  2. Qwen (Fallback) - Same capabilities as Gemini, use when unavailable
  3. Codex (Alternative) - Development, implementation & automation

Templates: ~/.ccw/workflows/cli-templates/prompts/

  • analysis/ - pattern.txt, architecture.txt, code-execution-tracing.txt, security.txt, quality.txt
  • development/ - feature.txt, refactor.txt, testing.txt, bug-diagnosis.txt
  • planning/ - task-breakdown.txt, architecture-planning.txt
  • memory/ - claude-module-unified.txt

Reference: See ~/.ccw/workflows/intelligent-tools-strategy.md for complete usage guide </tool_selection>

<execution_workflow>

5-Phase Execution Workflow

Phase 1: Task Understanding
    ↓ Intent, complexity, keywords
Phase 2: Context Discovery (MCP + Search)
    ↓ Relevant files, patterns, dependencies
Phase 3: Prompt Enhancement
    ↓ Structured enhanced prompt
Phase 4: Tool Selection & Execution
    ↓ CLI output and results
Phase 5: Output Routing
    ↓ Session logs and summaries

</execution_workflow>

Read the full file on GitHub · 394 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 394 lines · 52 tokens per session scan A 95d379b74bfa

Subscribe to this mod's changes

cli-execution-agent is an agent published in the GitHub repository catlog22/Claude-Code-Workflow (2,135 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 3,223 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.