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-quiz)<a href="https://agentmods.dev/commands/mnthe/hardworker-marketplace/ultrawork-quiz"><img src="https://agentmods.dev/badge/commands/mnthe/hardworker-marketplace/ultrawork-quiz/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-quiz"><img src="https://agentmods.dev/badge/commands/mnthe/hardworker-marketplace/ultrawork-quiz.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.02181 |
| Opus 5 | $0.00008 | $0.01091 |
| Sonnet 5 | $0.00003 | $0.00436 |
| Haiku 4.5 | $0.00002 | $0.00218 |
Grade A, and why
ultrawork-quiz 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 11d 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ultrawork Quiz Command
Overview
Test knowledge gained during ultrawork sessions. Quiz focuses on learnings and discoveries from codebase exploration, design decisions, and technical patterns, NOT mechanical facts the user already knows.
Session ID Handling
The session_id is provided by the hook via systemMessage as CLAUDE_SESSION_ID.
You MUST pass it to scripts via --session flag.
Options
| Option | Default | Description |
|---|---|---|
--count N |
5 | Number of quiz questions |
--session ID |
current | Session to quiz on (uses CLAUDE_SESSION_ID if omitted) |
Quiz Data Sources
Priority Order
-
exploration/*.md (High priority)
- Tech stack discoveries
- Architecture patterns
- Naming conventions
- Framework/library usage
-
docs/plans/*.md (High priority)
- Design rationale
- Approach comparisons
- Decision reasoning
- Trade-off analysis
-
tasks/*.json criteria (Medium priority)
- Verification methods
- Test commands
- Success patterns
-
evidence_log (Low priority)
- Tools/commands actually used
- Test execution patterns
What to Include
✅ Focus on learnings:
- "What scripting runtime was discovered?" (Bun)
- "Why was approach X chosen over Y?" (Design rationale)
- "What naming convention is used for components?" (Pattern)
- "Which framework does this project use?" (Tech stack)
❌ Exclude mechanical facts:
- Session goal (user already knows)
- Task names/completion status (not a learning)
- "Was file X modified?" (not discovery)
Workflow
Phase 1: Parse Arguments
# Parse --count and --session from user input
# Default count: 5
# Default session: CLAUDE_SESSION_ID
Phase 2: Read Session Data
# Get session metadata
bun "${CLAUDE_PLUGIN_ROOT}/src/scripts/session-get.js" --session ${SESSION_ID} --field working_dir
# Get session directory
SESSION_DIR=~/.claude/ultrawork/sessions/${SESSION_ID}
Phase 3: Collect Quiz Content
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.
- 11d ago First seen · 349 lines · 15 tokens per session scan A 11c1b2a73121
ultrawork-quiz 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 2,181 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
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-13-4.en
Welcome to Lesson 13-4: Landing Page Implementation!
start-0-8
A Japanese-language command that displays the current project setup progress.