ultrawork-quiz

ultrawork-quiz is a command for Claude Code from mnthe/hardworker-marketplace. It costs 15 tokens per session (2,181 once invoked), scanned A, original, MIT.

An interactive command that quizzes you about discoveries made during an Ultrawork session. It uses session notes, plans, task criteria, and recorded evidence to create questions about the project.

In plain words
What is it for?
Use it to review architecture discoveries, technology choices, naming conventions, design reasoning, verification methods, and tools used during an Ultrawork session.
Why use it?
It checks whether important project-specific lessons and decisions were understood, instead of testing only general technical facts. This can reveal gaps after exploring or changing a codebase.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the ultrawork plugin — 15 skills, 9 commands shipped together

Good fit Use it to review architecture discoveries, technology choices, naming conventions, design reasoning, verification methods, and tools used during an Ultrawork session.

Compare 6 commands from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add mnthe/hardworker-marketplace
Claude Code
/plugin install ultrawork

Made for: Claude Code.

Or install ultrawork, the plugin that ships this one along with the rest of its 15 skills, 9 commands.

Wrote 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.

agentmods badge for ultrawork-quiz

README.md
[![agentmods](https://agentmods.dev/badge/commands/mnthe/hardworker-marketplace/ultrawork-quiz/github.svg)](https://agentmods.dev/commands/mnthe/hardworker-marketplace/ultrawork-quiz)
Your own site
<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.

agentmods 80×15 button for ultrawork-quiz

Your own site · 80×15
<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>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,181 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 11d ago against content hash 11c1b2a73121, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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.

plugins/ultrawork/commands/ultrawork-quiz.md · 349 lines

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

  1. exploration/*.md (High priority)

    • Tech stack discoveries
    • Architecture patterns
    • Naming conventions
    • Framework/library usage
  2. docs/plans/*.md (High priority)

    • Design rationale
    • Approach comparisons
    • Decision reasoning
    • Trade-off analysis
  3. tasks/*.json criteria (Medium priority)

    • Verification methods
    • Test commands
    • Success patterns
  4. 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

Read the full file on GitHub · 349 lines

Changes

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.

  1. 11d ago First seen · 349 lines · 15 tokens per session scan A 11c1b2a73121

Subscribe to this mod's changes

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.