command-to-subagent

A guide for moving a command's complex execution work into a subagent, a separate agent focused on carrying out a specific task.

In plain words
What is it for?
Use it when converting commands with heavy API or MCP calls, reducing recipe context, or separating a confirmation workflow from execution logic.
Why use it?
It keeps the user-facing command focused on input, preview, confirmation, and dispatch while isolating API or MCP work.

Skill for Claude CodeCodex

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 skills/patrickclery/ruly/command-to-subagent
Any agent
npx skills add patrickclery/ruly --skill command-to-subagent
Clone the repo
git clone --depth 1 https://github.com/patrickclery/ruly

Made for: Claude Code, Codex.

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,338 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.00042 $0.01338
Opus 5 $0.00021 $0.00669
Sonnet 5 $0.00008 $0.00268
Haiku 4.5 $0.00004 $0.00134

Measured 2d ago against content hash 9cdd2c706827, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

command-to-subagent 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 2d ago.

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/ruly/skills/command-to-subagent/SKILL.md · 210 lines

How it starts

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

Converting Commands to Subagents

Overview

Extract execution logic from a command into a dedicated subagent, keeping only the user-facing workflow (preview, confirmation) in the command. This reduces recipe context by isolating API/MCP complexity.

When to Use

  • Command has heavy MCP or API call logic
  • Want to reduce token usage in a recipe
  • Need to isolate execution complexity from user workflow
  • Command follows preview → confirm → execute pattern

Quick Reference

Component Location Contains
Command commands/{name}.md User workflow (preview, confirm, dispatch)
Subagent agents/{name}.md Execution logic (MCP calls, API operations)
Recipe recipes.yml Subagent registration

Conversion Steps

Step 1: Identify the Split Point

Find where user interaction ends and execution begins:

User workflow (COMMAND):     Execution (SUBAGENT):
├─ Parse input               ├─ API/MCP calls
├─ Validate/lookup           ├─ Error handling
├─ Show preview              ├─ Response formatting
├─ Handle revisions          └─ Return structured result
└─ Dispatch on confirm

Split at confirmation - everything after "send it" / "post it" goes to subagent.

Step 2: Create the Subagent File

Location: rules/{domain}/agents/{name}.md

Structure:

---
description: Instructions for the {name} subagent when dispatched
alwaysApply: true
requires:
  - ../common.md        # Shared patterns
  - ../../accounts.md   # If needs user lookups
---
# {Name} Subagent - EXECUTION REQUIRED

## ⚠️ CRITICAL: You MUST Execute

**Your ONLY job is to {action}.** If you complete with "0 tool uses", you have FAILED.

## Input Format

You will receive a prompt like:
{show expected input structure}

## Execution Steps

### Step 1: {First action}
{MCP/API call with example}

### Step 2: {Next action}
...

### Step N: Return Result

**On success:**
```json
{"status": "success", "field": "value"}

On error:

{"status": "error", "error": "message", "step": "which failed"}

Failure Conditions

FAILED if you:

  • Complete with "0 tool uses"
  • Return without executing
  • Ask clarifying questions

SUCCESS if you:

  • Execute all required steps
  • Return structured result

Read the full file on GitHub · 210 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. 2d ago First seen · 210 lines · 42 tokens per session scan A 9cdd2c706827

Subscribe to this mod's changes

command-to-subagent is a skill published in the GitHub repository patrickclery/ruly (5 stars, last pushed 7d ago), licensed MIT. It adds 42 tokens to every session and 1,338 once invoked, about $0.0002 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-31.