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 agentmods add skills/sandsower/beislid/reviewnpx skills add sandsower/beislid --skill reviewgit clone --depth 1 https://github.com/sandsower/beislidWrote 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/sandsower/beislid/review)<a href="https://agentmods.dev/skills/sandsower/beislid/review"><img src="https://agentmods.dev/badge/skills/sandsower/beislid/review.svg" alt="Measured on agentmods" 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.00050 | $0.01644 |
| Opus 5 | $0.00025 | $0.00822 |
| Sonnet 5 | $0.00010 | $0.00329 |
| Haiku 4.5 | $0.00005 | $0.00164 |
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 5d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review
Review a diff against requirements and return findings. This is a primitive, not a workflow.
review may read files, inspect diffs, and classify findings. It must not edit files, commit, push, post comments, update tickets, create PRs, or run a fix loop. Callers decide what to do with the findings.
Use this for:
- Pre-PR local diff review from
ready-for-review - Ad-hoc "review my changes" requests
- Reviewing a supplied patch/diff
- A reusable review contract for
fresh-eyes,rinse, andpr-patrolworkflows
If the repo declares custom lifecycle hooks, read ../lifecycle-hooks.md and honor any phase-boundary hooks before and after review.
Do not use this for:
- A final whole-diff pass after iterative fixes — use
fresh-eyes - Interactive walkthroughs of your own diff — use
walk-the-diff - Reviewing someone else's GitHub PR and posting comments — use
pr-patrol - Security-only audits — use a security audit workflow if available
- Fixing findings — return findings to the caller
If the reviewer explicitly wants a durable visual artifact for the diff, evidence, or explanation, suggest show-me and wait for the user to ask. Do not auto-run show-me from review in v1.
Process
1. Establish the input
Accept one of:
- Caller-supplied diff/range/context
- Local git diff against a base branch
- Pasted patch/diff
If reviewing local changes and the caller did not supply a range:
git status --short
gh pr view --json baseRefName,headRefName 2>/dev/null
git merge-base HEAD main # or master / PR base when applicable
git diff <base-sha>...HEAD --stat
git diff <base-sha>...HEAD
If the base is unclear, ask once.
2. Load requirements/context
Prefer context supplied by the caller. Otherwise look lightly for:
plans/*-design.mdplans/*-spec.mdplans/*-structure.md- matching
break_spec_approved,spec_approved, orblueprint_approvedlatest pointer entries when the ticket uses custom artifact locations - Ticket/issue summary if available in the conversation
- Commit messages in the review range
What ships with it
1 file 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.
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.
- 5d ago First seen · 198 lines · 50 tokens per session scan A 465a4886a140
review is a skill published in the GitHub repository sandsower/beislid (10 stars, last pushed 6d ago), licensed MIT. It adds 50 tokens to every session and 1,644 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…