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/mnthe/hardworker-marketplaceWrote 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-help)<a href="https://agentmods.dev/commands/mnthe/hardworker-marketplace/ultrawork-help"><img src="https://agentmods.dev/badge/commands/mnthe/hardworker-marketplace/ultrawork-help/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/mnthe/hardworker-marketplace/ultrawork-help"><img src="https://agentmods.dev/badge/commands/mnthe/hardworker-marketplace/ultrawork-help.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.00015 | $0.00906 |
| Opus 5 | $0.00008 | $0.00453 |
| Sonnet 5 | $0.00003 | $0.00181 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
ultrawork-help 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 9d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ultrawork Help
Explain the following to the user:
What is Ultrawork?
Ultrawork is a strict verification-first development mode that enforces rigorous practices:
┌─────────────────────────────────────────────────────────────┐
│ │
│ ✓ Mandatory planning via planner agent │
│ ✓ Success criteria defined BEFORE implementation │
│ ✓ Evidence collection for every criterion │
│ ✓ Zero tolerance for partial completion │
│ ✓ Parallel worker execution for maximum speed │
│ │
└─────────────────────────────────────────────────────────────┘
Available Commands
| Command | Description |
|---|---|
/ultrawork-plan <goal> |
Interactive planning → creates plan document |
/ultrawork-exec [file] |
Execute plan document |
/ultrawork <goal> |
Full auto mode (plan + exec) |
/ultrawork-status |
Check current phase and progress |
/ultrawork-evidence |
View collected evidence |
/ultrawork-clean |
Clean up project workspace |
/ultrawork-help |
Show this help |
Recommended Workflow
/ultrawork-plan "implement auth" # Interactive planning with user
→ Review/edit docs/ultrawork-plan.md
/ultrawork-exec # Execute approved plan
Options (for /ultrawork)
| Option | Description |
|---|---|
--max-workers N |
Limit parallel workers |
--plan-only |
Only run planner, don't execute |
--force |
Force start even if session exists |
--resume |
Resume cancelled/failed session |
Workflow
/ultrawork "implement feature X"
│
▼
┌─────────────────────────────────────────┐
│ 1. PLANNING │
│ → Planner agent (opus) creates tasks │
│ → Spawns explorers for context │
│ → Defines success criteria │
└─────────────────┬───────────────────────┘
▼
┌─────────────────────────────────────────┐
│ 2. EXECUTION │
│ → Workers implement in parallel │
│ → Each worker collects evidence │
│ → Tasks unblock as deps complete │
└─────────────────┬───────────────────────┘
▼
┌─────────────────────────────────────────┐
│ 3. VERIFICATION │
│ → Verifier checks all evidence │
│ → Scans for blocked patterns │
│ → Runs tests and builds │
└─────────────────┬───────────────────────┘
▼
┌─────────────────────────────────────────┐
│ 4. COMPLETE │
│ → All criteria met with evidence │
│ → Summary reported │
└─────────────────────────────────────────┘
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.
- 9d ago First seen · 132 lines · 15 tokens per session scan A 94254c89fda6
ultrawork-help is a command published in the GitHub repository mnthe/hardworker-marketplace (4 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 906 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.