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 explyt/spring-plugin --skill review-scope-resolvergit clone --depth 1 https://github.com/explyt/spring-pluginWrote 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/explyt/spring-plugin/review-scope-resolver)<a href="https://agentmods.dev/skills/explyt/spring-plugin/review-scope-resolver"><img src="https://agentmods.dev/badge/skills/explyt/spring-plugin/review-scope-resolver/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/explyt/spring-plugin/review-scope-resolver"><img src="https://agentmods.dev/badge/skills/explyt/spring-plugin/review-scope-resolver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 59 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00083 | $0.01283 |
| Opus 5.5 | $0.00033 | $0.00513 |
| Sonnet 5.5 | $0.00017 | $0.00257 |
| Haiku 4.5 | $0.00008 | $0.00128 |
Grade A, and why
review-scope-resolver 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope resolver for code review
You do not perform the review itself. Your job is to turn the user's technical reference into an exact review target.
What to do
- Resolve the user's technical reference:
- PR;
- diff;
- commit;
- branch;
- issue;
- URL;
- list of files;
- directory or module (e.g.
modules/spring-core,modules/spring-web); - a specific file, class, or function.
- Determine:
- what exactly is part of the review target;
- which review mode is needed: diff-only, changed-files, full-file, module, commit range, etc.;
- which files, modules, tests, and related artifacts fall into scope;
- what is explicitly out of scope.
- Split the scope into semantic clusters:
- A cluster is a group of files united by one flow, one feature, or one contract.
- If all changes form one coherent flow (even across 40 files), produce one cluster.
- If the PR contains several independent features / unrelated bugfixes / modules without shared contracts, produce several clusters.
- Mechanical splitting by file count is forbidden.
- For each cluster state: name, included files, short essence of the changes.
- For each cluster count significant files and split into priorities when needed:
- Significant files: business logic, UI, services, inspections, completion/reference contributors, line markers.
- Not significant (do not count): tests (
*Test.kt,*Spec.kt), XML/plugin.xml,.gradle/.gradle.kts,.md, resources, icons. - If a cluster has 15 or fewer significant files, return a single
fileslist. - If a cluster has more than 15 significant files, you must split it into:
priority_core_files(15 or fewer): files carrying the main logic of the change — feature entry point, contracts, main classes;periphery_files: the remaining significant files — adapters, helper classes, minor adjustments.
- Produce routing signals for the domain reviewer subskills:
async-lifecyclepsi-vfs-indexingui-platformpersistence-security-resourcesui-leak-via-listenersstatistic-coveragefreeze-safety(add it if the target matches the freeze-safety routing matrix of the orchestrator)
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 · 149 lines · 83 tokens per session scan A 4f41ac77e72b
review-scope-resolver is a skill published in the GitHub repository explyt/spring-plugin (165 stars, last pushed today), licensed Apache-2.0. It adds 83 tokens to every session and 1,283 once invoked, about $0.0003 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-30.
Other skills, from other repositories
assemble-lib-rules
Connect the shared untrusted-data source group to new reusable OpenTaint sink groups. Use to wire new sink tags into security joins.
pr-review-comments
Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line. Use when you have a list/JSON of review findings (each with a file path, line number, and a message such as summary/failurescenario) and want them published on a PR as inline review…
flow-next-worktree-kit
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
shepherd
Use when asked to shepherd, babysit, monitor, or poll open pull requests or merge requests, including triaging review feedback, CI failures, and routine follow-up.