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/explyt/spring-plugin/review-context-buildernpx skills add explyt/spring-plugin --skill review-context-buildergit 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-context-builder)<a href="https://agentmods.dev/skills/explyt/spring-plugin/review-context-builder"><img src="https://agentmods.dev/badge/skills/explyt/spring-plugin/review-context-builder.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 | $0.00064 | $0.01731 |
| Opus 5 | $0.00032 | $0.00865 |
| Sonnet 5 | $0.00013 | $0.00346 |
| Haiku 4.5 | $0.00006 | $0.00173 |
Grade A, and why
review-context-builder 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 4d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review context builder
You do not produce final review findings. Your job is to build shared reusable context that benefits all reviewer subskills.
Inputs
The orchestrator must pass you:
- the exact review target;
- the path to
REVIEW_SCOPE.md; - an explicit focus for this context pass:
architecturetests-conventionsfreeze-safetycombined
- the path where the full result must be written.
What to collect
Depending on the focus:
architecture
Collect:
- affected modules (e.g.
modules/spring-core,modules/spring-web,modules/spring-data) and their dependencies; - integration points;
- contracts between components;
- side effects and hidden couplings;
- systemic risks for the review.
tests-conventions
Collect:
- related tests and test patterns (including
modules/test-frameworkusage); - lifecycle and disposal expectations;
- project conventions relevant to the target;
- observability, logging, and maintainability expectations;
- known risk areas.
freeze-safety
A specialized focus for user-perceived responsiveness (typing latency, scroll stutter, slow window opening, EDT freezes). Do not duplicate the reviewer subskill rules — only inventory hot paths and provide reasoning anchors.
Collect from the scope and surrounding code:
- Hot-path inventory — explicitly list the in-scope elements of each category with paths/names:
- renderers:
ListCellRenderer,TreeCellRenderer,TableCellRenderer,ColoredListCellRenderer,ColoredTreeCellRenderer,paintComponent, icons in hot render paths; - action updates:
AnAction.update,ActionPromoter,EditorActionHandler.isEnabledForCaret; - service init:
@Serviceconstructor /init {},projectOpened,StartupActivity,ProjectActivity; - UI open paths:
ToolWindowFactory.createToolWindowContent,DialogWrapper.createCenterPanel,Configurable.createComponent; - typing hot path:
CompletionContributor,Annotator,ExternalAnnotator,TypedHandlerDelegate,DocumentListener.documentChanged,LineMarkerProvider; - event handlers:
BulkFileListener,DocumentListener,CaretListener,SelectionListener,messageBussubscribers; - dispose paths:
dispose(),disposeUIResources(),projectClosed.
- renderers:
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.
- 4d ago First seen · 188 lines · 64 tokens per session scan A c1c30a802c57
review-context-builder is a skill published in the GitHub repository explyt/spring-plugin (160 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 1,731 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-30.
Other skills, from other repositories
spring-ecosystem-docs
Spring Boot 4.x + Framework 7.x — auto-configuration, DI, AOP, MVC, WebFlux, Security, Data JPA/MongoDB/Redis.
analyze-external-methods
Analyze an OpenTaint scan's dropped external methods and decide which of them are propagators and optionally sinks. Use when a dropped-external-methods.yaml needs classification for dropped method type.
create-rule
Author and verify an OpenTaint rule. Use whenever a rule creation is needed.
create-test-project
Create an OpenTaint test project with positive/negative samples for verifying a rule or approximation. Use when a rule or approximation needs a test project to check against.
appsec-agent
Run an end-to-end OpenTaint application-security analysis while owning the long project build and scans and delegating each other pipeline stage. Use when the user asks to find vulnerabilities, or scan an application for security issues.
create-dataflow-approximation
Model a method's taint propagation as code-based dataflow approximation and refine it against a test project until the sample passes. Use for a dropped method that requires code-based approximation.