Borrowing it
Nothing to install: this file belongs to davidmatousek/tachi. 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/davidmatousek/tachi/main/.claude/commands/execute.mdgit clone --depth 1 https://github.com/davidmatousek/tachiWrote 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/davidmatousek/tachi/execute)<a href="https://agentmods.dev/commands/davidmatousek/tachi/execute"><img src="https://agentmods.dev/badge/commands/davidmatousek/tachi/execute/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/davidmatousek/tachi/execute"><img src="https://agentmods.dev/badge/commands/davidmatousek/tachi/execute.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.00020 | $0.00650 |
| Opus 5.5 | $0.00008 | $0.00260 |
| Sonnet 5.5 | $0.00004 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
execute 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- execute — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Overview
Execute ad-hoc tasks with automatic agent assignment and parallel orchestration. Use for quick fixes, updates, and multi-file changes without the full triad workflow.
Input: Natural language task description (e.g., "Fix the OAuth bug and update docs")
Output: Completed tasks + Architect review (if code changes) + Execution summary
Agent Assignment
See Agent Registry for task-to-agent mapping.
| Pattern | Agent |
|---|---|
| api, endpoint, backend, database | senior-backend-engineer |
| component, ui, react, frontend | frontend-developer |
| test, validation, e2e | tester |
| deploy, docker, ci/cd, infrastructure | devops |
| debug, investigate, root cause | debugger |
| security, vulnerability, auth | security-analyst |
| design, mockup, ux | ux-ui-designer |
| research, evaluate, best practice | web-researcher |
| docs/architecture/ | architect |
| docs/devops/ | devops |
Workflow
Step 1: Parse Tasks
Split user input by "and", ",", "then", ";" into discrete tasks. Classify each by keywords from the Agent Registry.
Step 2: Assign Agents
Map each task to primary agent using the Agent Registry table.
Step 3: Compute Waves
- Wave 1: Tasks with no dependencies (can run in parallel)
- Wave 2+: Tasks that depend on previous waves
- Sequential keywords ("then", "after") create dependencies
Step 4: Execute
Launch agents in parallel within each wave using Task tool. Wait for wave completion before starting next wave.
Step 5: Architect Review
If any code was changed, invoke architect agent to review technical decisions.
Step 6: Summary
Report completed tasks, files modified, wave timings, and any issues.
Examples
Quick fix:
/execute Fix the login redirect bug and add a test for it
→ Wave 1: debugger (fix) → Wave 2: tester (test)
Parallel work:
/execute Add logging to the API, update the README
→ Wave 1: senior-backend-engineer + product-manager (parallel)
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.
- 1mo ago First seen · 94 lines · 20 tokens per session scan A 71be2f015d33
execute is a command published in the GitHub repository davidmatousek/tachi (94 stars, last pushed 4d ago), licensed Apache-2.0. It adds 20 tokens to every session and 650 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
challenge
Run cs-security-analyst (AT workflow) against the Perfect Storm 8-vector crisis scenario and produce a 12-check mock comparison scorecard.
test
Run a USAP skill against the FortiGate zero-day test scenario and produce a 6-problem compliance scorecard.
run
Load a USAP skill SKILL.md and activate it as your operating persona. Argument: skill slug.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.