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 GentBajko/capstone --skill reviewgit clone --depth 1 https://github.com/GentBajko/capstoneWrote 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/gentbajko/capstone/review)<a href="https://agentmods.dev/skills/gentbajko/capstone/review"><img src="https://agentmods.dev/badge/skills/gentbajko/capstone/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/gentbajko/capstone/review"><img src="https://agentmods.dev/badge/skills/gentbajko/capstone/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.00113 | $0.00262 |
| Opus 5.5 | $0.00045 | $0.00105 |
| Sonnet 5.5 | $0.00023 | $0.00052 |
| Haiku 4.5 | $0.00011 | $0.00026 |
Grade A, and why
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 29d 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
Capstone: review
From this skill's base directory, read ../core/references/core.md
and ../core/references/core-authoring.md, then execute
../core/references/protocols/review.md
exactly (review is core.md's sole judgment exception). No argument
runs both sides; backend/be or frontend/fe runs one.
retro is the exception: review retro [session] executes
../core/references/protocols/retro.md
exactly instead, and review.md is not read. An argument after it
names the session; with none, it reads the session in progress.
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.
- 29d ago Changed · +5 lines · +39 tokens per session 04d97b96d818
- 1mo ago First seen · 13 lines · 74 tokens per session scan A 0534c0000562
review is a skill published in the GitHub repository GentBajko/capstone (5 stars, last pushed 29d ago), licensed Apache-2.0. It adds 113 tokens to every session and 262 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
reviewer
Validate proposals before implementation and generate ADR/PR documentation. Forces structured review of plans, architecture decisions, and code changes before executing. Use when making significant changes, starting new features, refactoring, or when uncertainty exists. Triggers on: review this, validate, does this…
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
spike-consumer-baseline
OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIALID and data path.
spike-guidance-inline
OI-3 spike harness — the INLINE (non-forked) readability-guidance variant. Surfaces the shared readability standard into the calling skill's own context. Use only when a spike consumer skill invokes it.
guidance
Authoritative guidance for building Claude Code skills, agents, and plugins, vendored into this repository. Use when you need the rules or best practices for a skill, agent, hook, or plugin — designing, reviewing, hardening, or checking one against the guidance. Does not run an interview to build a new skill or agent…
spike-consumer-adversarial
OI-3 spike harness — heavy consumer, ADVERSARIAL arm. Worst-case early-exit test: the mid-workflow Skill call has no continuation guardrail and the guidance skill ends with a final-sounding anchor. Use only when explicitly invoked by the spike harness with a TRIALID and data path.