Borrowing it
Nothing to install: this file belongs to Smart-AI-Memory/empathy-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Smart-AI-Memory/empathy-framework/main/.claude/commands/agent.mdgit clone --depth 1 https://github.com/Smart-AI-Memory/empathy-frameworkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/smart-ai-memory/empathy-framework/agent)<a href="https://agentmods.dev/commands/smart-ai-memory/empathy-framework/agent"><img src="https://agentmods.dev/badge/commands/smart-ai-memory/empathy-framework/agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/smart-ai-memory/empathy-framework/agent"><img src="https://agentmods.dev/badge/commands/smart-ai-memory/empathy-framework/agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00013 | $0.01721 |
| Opus 5.5 | $0.00005 | $0.00688 |
| Sonnet 5.5 | $0.00003 | $0.00344 |
| Haiku 4.5 | $0.00001 | $0.00172 |
Grade A, and why
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 2mo 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Management
Aliases: /agents
Create, configure, and orchestrate specialized agents.
Quick Examples
/agent # Interactive menu
/agent "create code review" # Create new agent
/agent "list available" # List agents
Discovery
Question:
header: "Task"
question: "What would you like to do with agents?"
options:
- label: "Create new agent"
description: "Define a new specialized agent"
- label: "Create agent team"
description: "Assemble agents for collaborative work"
- label: "List agents"
description: "View available agents and their capabilities"
- label: "Invoke agent"
description: "Run a specific agent for a task"
Create New Agent
Define a new specialized agent in markdown format.
Tell me:
- Agent name and purpose
- What tasks it should handle
- Any special tools or permissions needed
I will:
- Create agent markdown file in
agents_md/ - Define appropriate:
- Role and description
- Tool permissions
- Model tier (cheap/capable/premium)
- Empathy level (1-5)
- Add detailed instructions
- Register in the agent registry
Agent file format:
---
name: my-agent
description: What this agent does
role: specialist
tools: [Read, Grep, Glob]
model_tier: capable
empathy_level: 3
---
# Agent Instructions
Detailed instructions for the agent...
Create Agent Team
Assemble multiple agents for collaborative work using one of 10 composition patterns.
Tell me:
- Team purpose
- What agents should be included
- Workflow type (or let me auto-select based on task)
I will:
- Select appropriate agents
- Choose optimal composition pattern (from 10 available)
- Set up handoff points
- Configure aggregation of results
Available Composition Patterns:
| Pattern | When to Use | Example |
|---|---|---|
| sequential | Step-by-step pipeline | Parse → Analyze → Report |
| parallel | Independent tasks | Security + Quality + Performance audits |
| debate | Multiple perspectives | 3 reviewers discuss approach |
| teaching | Expert validates junior | Draft (cheap) → Expert review |
| refinement | Iterative improvement | Draft → Review → Polish |
| adaptive | Dynamic routing | Classifier → Specialist |
| conditional | Branch by condition | If bug → Debugger, else Reviewer |
| tool_enhanced (NEW) | Single agent + tools | File reader with analysis tools |
| prompt_cached_sequential (NEW) | Shared large context | 3 agents using same docs/codebase |
| delegation_chain (NEW) | Hierarchical coordination | Coordinator → Specialists (≤3 levels) |
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.
- 2mo ago First seen · 251 lines · 13 tokens per session scan A dc9de27ce5b3
agent is a command published in the GitHub repository Smart-AI-Memory/empathy-framework (13 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,721 once invoked, about $0.0001 per session on Opus 5.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.
Other commands, from other repositories
workflow-classify
Classify task size (S/M/L/XL) and recommend the appropriate workflow pipeline.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
create-task-list.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.