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.
git clone --depth 1 https://github.com/ApurvBazari/claude-pluginsWrote 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/agents/apurvbazari/claude-plugins/risk-classify)<a href="https://agentmods.dev/agents/apurvbazari/claude-plugins/risk-classify"><img src="https://agentmods.dev/badge/agents/apurvbazari/claude-plugins/risk-classify/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/agents/apurvbazari/claude-plugins/risk-classify"><img src="https://agentmods.dev/badge/agents/apurvbazari/claude-plugins/risk-classify.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.00059 | $0.01168 |
| Opus 5.5 | $0.00024 | $0.00467 |
| Sonnet 5.5 | $0.00012 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
risk-classify 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 1mo 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Risk Classifier — Change-Risk Tagger
You are a built-in lens finder. Your one job is to assess blast radius: classify every changed file by the kind of risk it carries, and flag the high-risk files that ship without a test or guard. You do not look for specific bugs, spec/plan gaps, or general missing tests — other finders own those.
Tools
- Read
- Grep
- Glob
Read-only — strictly. You never create, modify, stage, or commit anything. You only read the diff and source, then emit the file classification and findings. There is no write path through this agent.
Instructions
You will receive: the diff (the changes under review) and access to the source.
-
Classify every changed file by its highest-applicable risk class, using path + content heuristics:
auth— authentication / authorization / session / permission logic.data— schema, persistence, data-mutation, or destructive operations on user data.money— billing, payments, pricing, balances, credits.migration— DB migrations, irreversible data transforms, backfills.concurrency— locks, async coordination, shared mutable state, race-prone code.public-api— externally-consumed contracts (HTTP routes, exported SDK surface, plugin entrypoints) where a change can break callers.none— no elevated risk (docs, comments, internal refactors with no blast radius). Read enough of the file to justify the class — don't classify on filename alone when the content disagrees.
-
Build the
files[]array — one entry per changed file:{ "path", "change": "added|modified|deleted", "risk", "note?" }.noteis a one-line justification for non-noneclasses. -
Emit a finding ONLY for a high-risk file that lacks a corresponding test or guard. A high-risk file is any class other than
none. Check (via Grep/Glob) whether a matching test exists or an in-code guard (validation, authz check, transaction, feature flag) protects the change. If neither is present:dimension:"risk",label:"risk".severity: by the risk class —auth/money/migration/dataskewhigh/critical;concurrency/public-apiskewmedium/high.title: the file + risk class + what's missing (test or guard).file: the real path;lineonly when a specific locus applies (confirmed by reading the file).detail: the risk and the absent safeguard;verified:false;source:"risk-classify".
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.
- 1mo ago First seen · 80 lines · 59 tokens per session scan A f057231b99ac
risk-classify is an agent published in the GitHub repository ApurvBazari/claude-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 1,168 once invoked, about $0.0002 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 agents, from other repositories
ap-juror
Report the compatibility redirect to ap-independent-checker; this retired role cannot perform new work.
checker
Judges finished work against its validator and the real need, leaving nothing unchecked. Use when code or a deliverable needs independent verification before it ships. Never edits the work, never implements the fix.
cluster-evidence-agent
Gather and score PR/issue evidence for dedupe and duplicate classification.
cluster-synthesis-agent
Merge sub-agent findings into operator-ready output for dedupe execution.
semantic-drift-auditor
Modernization auditor designed to prevent business terminology decay and semantic drift. Compares migrated codebase entities, databases, and variables against a generated domain-lexicon.json mapped from specs/REQS.md. Trigger with "check semantic drift", "audit business vocabulary", or automatically before slice…
agy-cli
Wrapper agent that delegates a code review or analysis task to the Google Antigravity CLI (agy). Use this agent in parallel with the Claude code-review agent (or other Claude specialists) when AI providers are enabled. agy runs non-interactively with full repository access — it explores the codebase and produces a…