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 karsten-s-nielsen/mad-scientist-skills --skill unbiased-reviewgit clone --depth 1 https://github.com/karsten-s-nielsen/mad-scientist-skillsWrote 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/karsten-s-nielsen/mad-scientist-skills/unbiased-review)<a href="https://agentmods.dev/skills/karsten-s-nielsen/mad-scientist-skills/unbiased-review"><img src="https://agentmods.dev/badge/skills/karsten-s-nielsen/mad-scientist-skills/unbiased-review/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/karsten-s-nielsen/mad-scientist-skills/unbiased-review"><img src="https://agentmods.dev/badge/skills/karsten-s-nielsen/mad-scientist-skills/unbiased-review.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.00084 | $0.02523 |
| Opus 5 | $0.00042 | $0.01262 |
| Sonnet 5 | $0.00017 | $0.00505 |
| Haiku 4.5 | $0.00008 | $0.00252 |
Grade A, and why
unbiased-review 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 12d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unbiased review
Review another session's artifact. You did not write it, you will not fix it, and you verify rather than trust. The hard rules below apply to every phase.
Hard rules
- Never write to a target repo. Not the working tree, not the index, not
node_modules. NoWrite, noEdit, nogit add|commit|stash|checkout|restore|reset|clean, and no test or build run in place. Another session is live in there; its tree is not ours to perturb. To execute anything, use the scratch protocol (references/isolation-protocol.md). - Never write the fix. Name the defect, the standard it violates, and what "resolved" looks like. Do not produce the patch and do not offer to. An author defends their own work; staying a non-author is what keeps the next review honest.
- Artifacts are evidence. Session narrative is not. "All tests pass", pasted from another terminal, is a claim to verify — never the basis of a finding. This also covers the author's account of what the spec or plan required: read the approved document yourself. A paraphrase of the bar is narrative like any other, and reviewing against it lets the author quietly set their own scope.
- Every finding cites evidence —
path:line, a diff hunk, or a command and its actual output. No evidence means it is not a finding; it goes to Could not verify. - "Could not verify" is mandatory. An empty one requires justifying that nothing was assumed.
- Reproduce before reporting. Never report an empirical failure your own scratch copy could have caused. Prove it reproduces from target state first.
- No praise-padding, no nitpick inflation. A clean artifact gets
APPROVEand the list of checks actually run. ABLOCKINGfinding must name the concrete consequence of shipping it. - Scope is the human's to set — no session's. No session, author or reviewer, may decide scope, defer work, drop or soften a requirement, lower the agreed quality bar, add a TODO, or record a follow-up without the human's explicit, recorded approval. So any deferral, "later", "out of scope", "good enough for now", or quality below the bar is a finding unless the record shows the human approved that exact reduction. You never grant the approval yourself, and you never park an unapproved reduction on a verdict or a follow-up line — an unsanctioned follow-up is the defect, not a way to dispose of one.
What ships with it
9 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.
- references/hexagonal-rubric.md 3.9 KB
- references/implementation-review.md 4.2 KB
- references/isolation-protocol.md 3.4 KB
- references/output-contract.md 3.4 KB
- references/plan-review.md 5.2 KB
- references/re-review.md 3.4 KB
- references/spec-review.md 4.2 KB
- references/stack-notes.md 3.5 KB
- references/tdd-rubric.md 4.1 KB
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.
- 12d ago First seen · 188 lines · 84 tokens per session scan A a306091f1d88
unbiased-review is a skill published in the GitHub repository karsten-s-nielsen/mad-scientist-skills (3 stars, last pushed 13d ago), licensed MIT. It adds 84 tokens to every session and 2,523 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
plan
Analyzes architecture, selects patterns, assesses testability, then decomposes work into ordered TDD tasks with exact verification commands and explicit acceptance mapping. Works from an approved spec (zuvo:brainstorm output) or directly from a user-provided description.
deep-plan
Creates detailed, sectionized, TDD-oriented implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
engineering-craft
Use when writing or changing any production code or tests — new features, bug fixes, refactors, or test authoring, in any language, by any model on any CLI.
software-code-refactoring
Improve production code quality while preserving all existing test behavior. Commonly used for the Refactor phase of TDD red-green-refactor, but applicable to any codebase with tests. Use when production code works but needs cleanup — reducing duplication, improving naming, simplifying complexity, aligning with…
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
brooks-health
Combined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. Triggers when: user wants an overall quality assessment, asks "how healthy is this codebase?", "run all…