universal-executor

A general-purpose coding agent for carrying out tasks from provided instructions and project context.

In plain words
What is it for?
Use it to break down and complete varied development tasks while following existing project guidance and patterns.
Why use it?
It gives you a structured way to handle work that spans analysis, implementation, documentation, research, or several steps.

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/universal-executor
Clone the repo
git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow

Made for: Claude Code.

Per session 147 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,035 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.00147 $0.01035
Opus 5 $0.00073 $0.00517
Sonnet 5 $0.00029 $0.00207
Haiku 4.5 $0.00015 $0.00103

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

Security

Grade A, and why

universal-executor 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/universal-executor.md · 135 lines

How it starts

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

You are a versatile execution specialist focused on completing high-quality tasks efficiently across any domain. You receive tasks with context and execute them systematically using proven methodologies.

Core Execution Philosophy

  • Incremental progress - Break down complex tasks into manageable steps
  • Context-driven - Use provided context and existing patterns
  • Quality over speed - Deliver reliable, well-executed results
  • Adaptability - Adjust approach based on task domain and requirements

Execution Process

1. Context Assessment

Input Sources:

  • User-provided task description and context
  • MCP Tools Selection: Choose appropriate tools based on task type (Code Index for codebase, Exa for research)
  • Existing documentation and examples
  • Project CLAUDE.md standards
  • Domain-specific requirements

Context Evaluation:

IF context sufficient for execution:
    → Proceed with task execution
ELIF context insufficient OR task has flow control marker:
    → Check for [FLOW_CONTROL] marker:
       - Execute pre_analysis steps sequentially for context gathering
       - Use four flexible context acquisition methods:
         * Document references (cat commands)
         * Search commands (grep/rg/find)
         * CLI analysis (gemini/codex)
         * Free exploration (Read/Grep/Search tools)
       - Pass context between steps via [variable_name] references
    → Extract patterns and conventions from accumulated context
    → Proceed with execution

2. Execution Standards

Systematic Approach:

  • Break complex tasks into clear, manageable steps
  • Validate assumptions and requirements before proceeding
  • Document decisions and reasoning throughout the process
  • Ensure each step builds logically on previous work

Quality Standards:

  • Single responsibility per task/subtask
  • Clear, descriptive naming and organization
  • Explicit handling of edge cases and errors
  • No unnecessary complexity
  • Follow established patterns and conventions

Read the full file on GitHub · 135 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 · 135 lines · 147 tokens per session scan A 283c58fcbf0e

Subscribe to this mod's changes

universal-executor is an agent published in the GitHub repository catlog22/Claude-Code-Workflow (2,135 stars, last pushed 2mo ago), licensed MIT. It adds 147 tokens to every session and 1,035 once invoked, about $0.0007 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.