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/panda850819/verbs/reviewnpx skills add panda850819/verbs --skill reviewgit clone --depth 1 https://github.com/panda850819/verbsWrote 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/panda850819/verbs/review)<a href="https://agentmods.dev/skills/panda850819/verbs/review"><img src="https://agentmods.dev/badge/skills/panda850819/verbs/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.00049 | $0.01074 |
| Opus 5 | $0.00024 | $0.00537 |
| Sonnet 5 | $0.00010 | $0.00215 |
| Haiku 4.5 | $0.00005 | $0.00107 |
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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
The delta beyond an unstructured single-pass review is scope provenance, risk-adaptive lanes, evidence gates, bounded correction, and cold escalation.
1. Bind scope
- Read
AGENTS.mdorCLAUDE.mdwhen present. - Resolve the base from the PR, upstream, or merge-base; print the base and changed-file list. Never silently review the whole repository.
- Read the issue, brief, or request that defines intent. If none exists, report
INTENT GAPand infer only from the diff. - Check branch state and uncommitted changes; use history only to explain scope.
2. Choose the risk lane
- low: local, reversible, with no trust boundary, persistent data, concurrency, public interface, generated contract, or production operation.
- medium: shared behavior, multiple files, compatibility, or concurrency.
- high: auth, secrets, money, permissions, migrations, destructive writes, production infrastructure, or unfamiliar costly behavior.
Choose the lane from the diff and intent. Promote when the first pass reveals a risk trigger, candidate finding, coverage gap, or scope drift.
Low-risk fast path
Only in the low lane with explicit scope and intent: trace the changed path,
match acceptance and branches to tests, and self-refute the likeliest defect. An
INTENT GAP promotes rather than entering this fast path. If no finding, gap, or
drift remains: Do not load review learnings; enumerate no lenses,
print no empty scope-drift or cold-review fields, and return:
Review scope: <base>..<head> | <n> files | risk: low
No actionable findings.
Coverage: <verified check>
Self-refute: <assumption and observed result>
3. Escalated review
Read lib/learning-recall.md and apply relevant repo learnings. Map the diff to
security, data integrity, concurrency, architecture, or operations lenses.
Medium uses only triggered lenses. High uses every relevant lens plus a
cold review.
Trace changed inputs through code, callers, contracts, tests, and failure
handling. A finding survives only with severity P0–P3, a tight file/line
range, a trigger, mechanism and user-visible consequence, and a correction
direction. Exclude style,
unreachable speculation, and pre-existing defects; review does not edit code.
What ships with it
2 files beside review-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 · 117 lines · 49 tokens per session scan A 1190d26df99e
review is a skill published in the GitHub repository panda850819/verbs (5 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 1,074 once invoked, about $0.0002 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
processing-markdown
Processes Markdown files using mq, a jq-like query language for Markdown. Use when the user mentions Markdown processing, content extraction, document transformation, or mq queries.
web-scraping
Fetches web pages and extracts structured data using mq's toolchain (mq-crawl for fetching/crawling/JS rendering, mq for HTML-to-Markdown selector-based extraction, http() for in-query requests). Use when the user wants to scrape a URL, pull structured data out of a webpage, crawl a site, or turn HTML into…
markstream-react
Integrate the beta markstream-react package into a React 18+ or Next app. Use when Codex needs to add the React renderer, choose the root, next, or server entrypoint, import CSS correctly, choose between content and nodes, keep client boundaries safe, add renderer-local streamingComponents or htmlComponents, use…
markstream-vue2-cli
Integrate markstream-vue2 into a Vue 2 Vue CLI or Webpack 4 app. Use when Codex needs Webpack 4-friendly setup, CDN worker fallbacks for Mermaid or KaTeX, dist/index.css imports, Vue 2 composition-api shims, or code block choices limited to stream-diffs or plain .
markstream-svelte
Integrate the beta markstream-svelte package in Svelte 5 or SvelteKit apps. Use when Codex needs Svelte 5 runes, CSS and optional peers, smooth streaming, worker setup, renderer-local or scoped custom components, or SSR-safe boundaries. Svelte 4 is unsupported.
[object Object]
Read, search, and open notes in the user's "{{GRAPHNAME}}" Reflect graph via the reflect CLI. Use when the user asks about their notes, daily notes, journal, or anything they may have written down in Reflect.