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.
npx skills add mnthe/hardworker-marketplace --skill ultraworkgit 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/skills/mnthe/hardworker-marketplace/ultrawork)<a href="https://agentmods.dev/skills/mnthe/hardworker-marketplace/ultrawork"><img src="https://agentmods.dev/badge/skills/mnthe/hardworker-marketplace/ultrawork/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/skills/mnthe/hardworker-marketplace/ultrawork"><img src="https://agentmods.dev/badge/skills/mnthe/hardworker-marketplace/ultrawork.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.00082 | $0.00953 |
| Opus 5 | $0.00041 | $0.00477 |
| Sonnet 5 | $0.00016 | $0.00191 |
| Haiku 4.5 | $0.00008 | $0.00095 |
Grade A, and why
ultrawork 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 10d 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 Mode
Overview
Ultrawork enforces verification-first development - a strict mode where every completion claim requires concrete evidence.
Core Principles
- No implementation without planning - Explore codebase, design approach, decompose into tasks
- No completion without evidence - Every criterion needs proof (command output, test results)
- No partial work accepted - "Should work" or "basic implementation" triggers automatic rejection
Workflow Phases
PLANNING → EXECUTION → VERIFICATION → COMPLETE
↑ │
└── (Ralph Loop on fail) ←┘
| Phase | Description | Key Outputs |
|---|---|---|
| Planning | Explore → Design → Task decomposition | design.md, tasks/*.json |
| Execution | Workers implement tasks in parallel waves | Code changes, evidence |
| Verification | Verifier audits ALL evidence against criteria | PASS/FAIL decision |
Activation
Start ultrawork with the /ultrawork command:
/ultrawork "your goal" # Interactive: asks questions, user approves plan
/ultrawork --auto "your goal" # Auto: decides autonomously, no confirmations
/ultrawork --plan-only "goal" # Planning only, no execution
Mode Selection
| Mode | Best For | User Interaction |
|---|---|---|
| Interactive (default) | Complex features, unclear requirements | Questions + approval |
Auto (--auto) |
Well-defined tasks, CI/CD | None |
Plan-only (--plan-only) |
Design review before implementation | Planning only |
When to Use
USE ultrawork for:
- Multi-file implementations (3+ files)
- Architecture changes or refactoring
- New features with design decisions
- Work requiring verification trails
DON'T use ultrawork for:
- Single-file edits or bug fixes
- Documentation updates
- Quick questions or exploration
- Tasks completable in < 5 minutes
Zero Tolerance Rules
Verification automatically FAILS if output contains blocked patterns.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 132 lines · 82 tokens per session scan A ff080f14ea47
ultrawork is a skill published in the GitHub repository mnthe/hardworker-marketplace (4 stars, last pushed 4mo ago), licensed MIT. It adds 82 tokens to every session and 953 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…