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.
git clone --depth 1 https://github.com/multiplex-ai/muggle-ai-teamsWrote 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/multiplex-ai/muggle-ai-teams/multi-execute)<a href="https://agentmods.dev/commands/multiplex-ai/muggle-ai-teams/multi-execute"><img src="https://agentmods.dev/badge/commands/multiplex-ai/muggle-ai-teams/multi-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/multiplex-ai/muggle-ai-teams/multi-execute"><img src="https://agentmods.dev/badge/commands/multiplex-ai/muggle-ai-teams/multi-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.00035 | $0.02304 |
| Opus 5.5 | $0.00014 | $0.00922 |
| Sonnet 5.5 | $0.00007 | $0.00461 |
| Haiku 4.5 | $0.00003 | $0.00230 |
Grade A, and why
multi-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 today.
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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Execute — Multi-Model Collaborative Execution
Route implementation tasks to the appropriate external model (Codex for backend, Gemini for frontend), acquire prototype diffs, refactor to production-grade code, and audit with dual-model review.
Usage
/multi-execute <task description>
/multi-execute .claude/plan/<feature-name>.md # Execute from a plan file
/multi-execute backend <task description> # Force backend-only (Codex)
/multi-execute frontend <task description> # Force frontend-only (Gemini)
Context
- Task: $ARGUMENTS
- Multi-model collaboration: Codex (backend authority) + Gemini (frontend authority) + Claude (orchestration + all file writes)
Your Role
You are the Execution Orchestrator. You route tasks to external models, receive their prototype diffs, refactor them to production quality, and apply changes. External models have zero filesystem write access — all modifications are made by Claude.
Core Protocols
- Language Protocol: Use English when interacting with tools/models, communicate with user in their language
- Code Sovereignty: External models have zero filesystem write access, all modifications by Claude
- Dirty Prototype Refactoring: Treat Codex/Gemini output as "dirty prototype" — must refactor to production-grade code
- Trust Rules: Backend logic follows Codex, Frontend design follows Gemini. Cross-domain opinions are reference only.
- Stop-Loss: Do not proceed to next phase until current phase output is validated
Multi-Model Call Specification
Call syntax (parallel: run_in_background: true, sequential: false):
# New session call
Bash({
command: "~/.claude/bin/codeagent-wrapper {{LITE_MODE_FLAG}}--backend <codex|gemini> {{GEMINI_MODEL_FLAG}}- \"$PWD\" <<'EOF'
ROLE_FILE: <role prompt path>
<TASK>
Requirement: <requirement>
Context: <project context>
</TASK>
OUTPUT: Expected output format
EOF",
run_in_background: true,
timeout: 3600000,
description: "Brief description"
})
# Resume session call
Bash({
command: "~/.claude/bin/codeagent-wrapper {{LITE_MODE_FLAG}}--backend <codex|gemini> {{GEMINI_MODEL_FLAG}}resume <SESSION_ID> - \"$PWD\" <<'EOF'
ROLE_FILE: <role prompt path>
<TASK>
Requirement: <requirement>
Context: <project context>
</TASK>
OUTPUT: Expected output format
EOF",
run_in_background: true,
timeout: 3600000,
description: "Brief description"
})
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.
- today First seen · 243 lines · 35 tokens per session scan A 80a959b13604
multi-execute is a command published in the GitHub repository multiplex-ai/muggle-ai-teams (2 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 2,304 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-10-22.
Other commands, from other repositories
pi-ui-design
HTML mockup generation via Gemini — from design spec to previewable prototype.
analyze-file
Deep analysis of a specific file using code-analyst sub-agent.
design-import
Scaffolds React components from a Claude Design handoff bundle and stops at files on disk: no stories, no tests, no pull request. Use when handed a claude.ai/design URL or a local bundle file; when that same scaffold should carry on through test generation, browser verification and an opened PR, run /ork:design-ship…
README
Repo-development slash commands (NOT part of the distributed plugin surface).
range-review
A read-only command for reviewing a range of Git changes, such as all pull requests merged for a release. It uses several review perspectives, checks findings against the source, and suggests how each finding should be handled.
checklist
Generate a custom checklist for the current feature based on user requirements.