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/baizhiyuan/finding-unknowns-skillWrote 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/baizhiyuan/finding-unknowns-skill/change-quiz)<a href="https://agentmods.dev/commands/baizhiyuan/finding-unknowns-skill/change-quiz"><img src="https://agentmods.dev/badge/commands/baizhiyuan/finding-unknowns-skill/change-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/baizhiyuan/finding-unknowns-skill/change-quiz"><img src="https://agentmods.dev/badge/commands/baizhiyuan/finding-unknowns-skill/change-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.00013 | $0.00211 |
| Opus 5 | $0.00006 | $0.00105 |
| Sonnet 5 | $0.00003 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
change-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 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.
What it actually says
change-quiz
Direct entry into Technique 8 (quiz) — comprehension is the merge gate.
Dispatch
- Read
skills/finding-unknowns/SKILL.mdfrom this plugin (or~/.claude/skills/finding-unknowns/SKILL.mdfor manual installs). - Run Technique 8 — Quiz exactly as specified: report first (Context, What changed,
How it interacts, Intuition), then 5–8 questions weighted toward deviations and
interaction effects, honest grading with miss classification, and the two-round stop
rule. Delegate to the
quiz-masteragent when installed — an examiner that did not write the change asks harder questions. - Treat the user's arguments as the change to examine (branch, diff range, or session description; default: working tree vs merge base):
$ARGUMENTS
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 · 24 lines · 13 tokens per session scan A ad62953a631e
change-quiz is a command published in the GitHub repository baizhiyuan/finding-unknowns-skill (5 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 211 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
tldr-review
One-line TLDR PR review comments (verdict first, no filler).
lfe-improve-architecture
Find deepening opportunities in the codebase — turn shallow modules into deep ones. Use in Phase 5 (Hygiene sub-pipeline) or when scheduled by session count.
security-sast
Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks.
tdd
Test-driven development with TodoWrite planning and comprehensive testing.
code-review
Automated code review with swarm intelligence.
wize-tea-review
Goal. A structured review of one story before its gate decision. Distinct from Shuri's wize-code-review (which audits code health). This one audits AC fulfillment, test discipline, and risk-spot coverage.