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.
npx agentmods add skills/patrickclery/ruly/command-to-subagentnpx skills add patrickclery/ruly --skill command-to-subagentgit clone --depth 1 https://github.com/patrickclery/rulyWhat 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.
| Model | Per session | Once 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 |
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.
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
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.
- 2d ago First seen · 210 lines · 42 tokens per session scan A 9cdd2c706827
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.
Other skills, from other repositories
mcporter
List, auth, and call MCP servers/tools from the terminal.
agent-messaging
Send and receive cryptographically signed messages between AI agents using the Agent Messaging Protocol (AMP). Use when the user asks to "send a message to an agent", "check agent inbox", "message another agent", "reply to a message", "notify an agent", or any inter-agent communication task.
📝 任务完成后归档
重要提醒: 每次完成复杂调试或开发任务后,主动执行此流程! 将学到的经验归档为 skill,供以后参考。不要等用户提醒。.
oracle
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
agent-mode
Unified tool for managing agent LLM modes (add, remove, update, list, switch).
agento11y-prod-setup
Sets up production evaluation and guardrails for a DEPLOYED AI agent in Grafana Agent Observability, grounded in the agent's own code and its real ingested traffic. The judgment layer on top of the agento11y skill: it reads the agent's source (system prompt, tools, entrypoint) AND samples its live traffic via gcx…