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 zookanalytics/gc-toolkit --skill review-demogit clone --depth 1 https://github.com/zookanalytics/gc-toolkitWrote 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/zookanalytics/gc-toolkit/review-demo)<a href="https://agentmods.dev/skills/zookanalytics/gc-toolkit/review-demo"><img src="https://agentmods.dev/badge/skills/zookanalytics/gc-toolkit/review-demo/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/zookanalytics/gc-toolkit/review-demo"><img src="https://agentmods.dev/badge/skills/zookanalytics/gc-toolkit/review-demo.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.00100 | $0.02722 |
| Opus 5.5 | $0.00040 | $0.01089 |
| Sonnet 5.5 | $0.00020 | $0.00544 |
| Haiku 4.5 | $0.00010 | $0.00272 |
Grade A, and why
review-demo 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 today.
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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The demo check
The demo check decides whether a change needs a visual to be understood, and delivers the right one when it does. Need comes first: would a reviewer understand this change better by seeing it than by reading the diff? Modality comes second: what is the cheapest visual that shows it? When no visual helps, the check approves with a one-line note and attaches nothing.
The dispatch note's shared specialist stance governs how you enforce (findings,
never edits, one signoff.sh verdict). This file is the visual lens. Whether the
change is correct is the correctness check's. Whether it is the right thing to
ship, and presents itself so the operator can decide, is the pm check's.
When triage adds it
Triage adds demo when the diff changes a surface a person looks at:
- a rendered page, component, board, or dashboard;
- a layout or styling change;
- a new or changed interactive flow;
- output a person reads in a terminal, such as a command's report.
Logic, refactors, internal plumbing, tests, and docs read as text need no
visual, and triage adds nothing for them. That is the common case. The default
check set is the baseline, correctness,triage, so under it demo runs only on
a diff triage added it to.
When it runs
The check index places demo at the open-as-draft phase. Triage adds it before
the PR exists, the refinery opens the PR as a draft, and this check runs against
that draft. The review bead carries review_branch, review_base and the pinned
reviewed_oid; the anchor carries the PR (pr_number, pr_url). Where the
rig's host deploys previews for pull requests, the draft has one. The PR does
not leave draft for human review until every pre-open and open-as-draft check
reads green, this one included.
Decide need
Read the anchor for what the change is for, then the diff at the pinned commit. Triage made a coarse call when it saw a surface in the diff. Yours is the fine call: does seeing the change explain it better than reading it? A change to a page's source that alters nothing the page renders, or a style change too small to notice in a capture, needs no visual.
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.
- today Changed · +1 lines 9ca2aec3109d
- 4d ago Changed · +15 lines eee49fdab358
- 5d ago Changed · +48 lines 086c4c5e116f
- 9d ago First seen · 143 lines · 100 tokens per session scan A d33955953f94
review-demo is a skill published in the GitHub repository zookanalytics/gc-toolkit (5 stars, last pushed today), licensed MIT. It adds 100 tokens to every session and 2,722 once invoked, about $0.0004 per session on Opus 5.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-10-09.
Other skills, from other repositories
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
aesthetic-instrument
A committed aesthetic in the sense of skills/committed-aesthetic/SKILL.md: every rule below is checkable, and every value was read out of the source — packages/board/public/index.html and greatcto-site/styles.css — rather than chosen to write this document.
committed-aesthetic
How to write — and how to use — a skill that IS one aesthetic rather than a catalogue of them. A catalogue lets an agent pick, and it picks the modal option; a committed aesthetic makes it execute one thing precisely, against rules you can check. Use when a design keeps coming out competent and forgettable, when…
product-design-director
Define product UX and visual direction from user goals, brand evidence, states, responsiveness, and accessibility. Use when the main question is what the experience should communicate or feel like.
screenshot-to-interface
Reconstruct a maintainable interface from screenshots or visual references. Use when fidelity to supplied visual evidence is the primary requirement.
well-actually
Use when you want pedantic, nitpicky, opinionated feedback on a site or project — the kind of feedback you'd get from Hacker News commenters, typography snobs, grammar pedants, and standards purists. Finds the things that professional reviewers skip because they're "too minor.".