Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add mnthe/hardworker-marketplace/plugin install ultraworkWrote 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/mnthe/hardworker-marketplace/ultrawork-exec)<a href="https://agentmods.dev/commands/mnthe/hardworker-marketplace/ultrawork-exec"><img src="https://agentmods.dev/badge/commands/mnthe/hardworker-marketplace/ultrawork-exec.svg" alt="Measured on agentmods" 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.00016 | $0.03410 |
| Opus 5 | $0.00008 | $0.01705 |
| Sonnet 5 | $0.00003 | $0.00682 |
| Haiku 4.5 | $0.00002 | $0.00341 |
Grade A, and why
ultrawork-exec 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 7d 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 — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ultrawork Exec Command
Execute a plan created by /ultrawork-plan. Includes automatic retry loop for failed tasks and verification.
Overview
/ultrawork-exec
↓
Load Session → Execute Tasks (waves) → Verify → Retry if failed
↓
Loop until: PASS or max_iterations reached
Delegation Rules (MANDATORY)
The orchestrator MUST delegate work to sub-agents. Direct execution is prohibited.
| Phase | Delegation | Direct Execution |
|---|---|---|
| Execution | ALWAYS via Task(subagent_type="ultrawork:worker") |
NEVER |
| Verification | ALWAYS via Task(subagent_type="ultrawork:verifier") |
NEVER |
| Documentation | ALWAYS via Task(subagent_type="ultrawork:documenter") |
NEVER |
Exception: User explicitly requests direct execution (e.g., "run this directly", "execute without agent").
Sub-agent Execution
Sub-agents can be run in foreground (default) or background mode. Choose based on the situation:
| Mode | When to Use |
|---|---|
| Foreground | Sequential tasks, need result immediately |
| Background | Parallel execution with worker pool limits |
Parallel execution: Call multiple Tasks in a single message for automatic parallelization.
Session ID Handling
All scripts require --session <id> flag.
Claude Code v2.1.9+ automatically replaces ${CLAUDE_SESSION_ID} with the actual session UUID.
# Use ${CLAUDE_SESSION_ID} directly - it gets auto-replaced
bun "${CLAUDE_PLUGIN_ROOT}/src/scripts/session-get.js" --session ${CLAUDE_SESSION_ID} --field phase
bun "${CLAUDE_PLUGIN_ROOT}/src/scripts/session-update.js" --session ${CLAUDE_SESSION_ID} --phase EXECUTION
bun "${CLAUDE_PLUGIN_ROOT}/src/scripts/task-list.js" --session ${CLAUDE_SESSION_ID} --format json
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.
- 7d ago First seen · 447 lines · 16 tokens per session scan A e6d1b04e9674
ultrawork-exec is a command published in the GitHub repository mnthe/hardworker-marketplace (4 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 3,410 once invoked, about $0.0001 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 commands, from other repositories
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.