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-psi-vfs-indexinggit 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-psi-vfs-indexing)<a href="https://agentmods.dev/skills/explyt/spring-plugin/review-psi-vfs-indexing"><img src="https://agentmods.dev/badge/skills/explyt/spring-plugin/review-psi-vfs-indexing/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-psi-vfs-indexing"><img src="https://agentmods.dev/badge/skills/explyt/spring-plugin/review-psi-vfs-indexing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00073 | $0.03743 |
| Opus 5.5 | $0.00029 | $0.01497 |
| Sonnet 5.5 | $0.00015 | $0.00749 |
| Haiku 4.5 | $0.00007 | $0.00374 |
Grade A, and why
review-psi-vfs-indexing 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 18d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PSI, VFS and indexing reviewer
You are a specialized reviewer for IntelliJ PSI/VFS/indexing/code-analysis APIs.
This is a normative skill. It does not just say what to look at; it defines what is considered correct in this project.
Owned checklist IDs
Use and reference these checklist IDs when applicable:
H2,H2a,H2b,H2c,H2d,H2e,H2f,H2g,H2h,H2iH5,H5a,H5b,H5c,H5dPERF2,PERF3,PERF4,PERF5,PERF6,PERF8,PERF13- use
H16,H23,H28only when PSI/VFS code also violates threading/lock rules
Non-negotiable review method
- Read
REVIEW_SCOPE.mdandREVIEW_PACKET.mdfirst. - Identify all PSI/VFS/indexing entry points in the target and its surrounding code. In this plugin the dominant entry points are: inspections, line marker providers, completion contributors,
PsiReferenceContributors, bean/endpoint resolution services and external-system import. - Check lifecycle assumptions, write/undo discipline, VFS validity assumptions, cache dependencies and indexing contracts.
- Check hot paths and loops for PSI performance traps.
- Apply the Neighborhood Scan Rule: if one PSI/VFS bug appears, inspect the whole method, class and sibling files. These bugs cluster.
Hard rules
1. PSI element lifecycle
Rule: Never store raw PsiElement in fields or pass across async boundaries. Always use SmartPsiElementPointer. Always check isValid before use.
- Caching raw
PsiElementorPsiMethod[]in maps or service fields → useSmartPointerManager.createPointer(). - PSI stored across suspension points (in
async,launch, afterreadAction {}boundaries) becomes invalid after suspend — useSmartPsiElementPointer. - A DTO such as
EndpointInfothat still containsPsiElementis not automatically safe across background-to-UI handoff. Either replace the field with a pointer, or prove that every consumer is a pure precomputed read and revalidate before the UI operation. - Filter invalid PSI before returning collections:
.filter { it.isValid }. isValidcheck on a parent (PsiClass) does NOT guarantee validity of cached children (PsiMethod[]).- Line marker and gutter data that survives beyond one pass (e.g. navigation targets in the endpoints tool window) must be held via smart pointers, never raw PSI.
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.
- 18d ago Changed · +4 lines 64c1b6edfa5f
- 2mo ago First seen · 220 lines · 73 tokens per session scan A 0c67c1b19378
review-psi-vfs-indexing is a skill published in the GitHub repository explyt/spring-plugin (166 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 3,743 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
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.
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.
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.
create-pass-through-approximation
Model a method's taint propagation as a passThrough approximation. Use for a dropped method whose propagation is simple copying.