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 develop-gutter-navigation-featuregit 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/develop-gutter-navigation-feature)<a href="https://agentmods.dev/skills/explyt/spring-plugin/develop-gutter-navigation-feature"><img src="https://agentmods.dev/badge/skills/explyt/spring-plugin/develop-gutter-navigation-feature/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/develop-gutter-navigation-feature"><img src="https://agentmods.dev/badge/skills/explyt/spring-plugin/develop-gutter-navigation-feature.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.00142 | $0.02988 |
| Opus 5.5 | $0.00057 | $0.01195 |
| Sonnet 5.5 | $0.00028 | $0.00598 |
| Haiku 4.5 | $0.00014 | $0.00299 |
Grade A, and why
develop-gutter-navigation-feature 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 16d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop or Repair a Gutter Navigation Feature (explyt/spring-plugin)
Produce a working, registered, wiring-tested RelatedItemLineMarkerProvider (or repair an existing one) on its own branch with a PR to main, using the platform facts verified in the #410/#411/#427 series.
Critical constraints
- Call the
coding-guardskill first and follow it for style, threading, SPDX headers, bundles, statistics and PR hygiene. Do not restate its rules here. - A provider has two independent entry points: highlighting (
collectSlowLineMarkers→collectNavigationMarkers) andNavigate | Related Symbol(RelatedItemLineMarkerGotoAdapter→collectNavigationMarkersdirectly). Any gate must exist in both; never "move the per-element gate up" into the batch method. setTargetRendereris inert on the Related Symbol path — it rendersGotoRelatedItem.customName/customContainerNameviaDefaultPsiElementCellRenderer. Presentation fixes that must hold on both surfaces need two mechanisms.- Never widen
moduleWithDependenciesAndLibrariesScopeto find a reference declared in library source:ModuleWithDependenciesScope.RootCalculator.calcRootsmaps every non-module order entry toOrderRootType.CLASSES, so a*-sources.jarroot is not in that scope at all. Never let a feature's answer depend on whether the user pressed Download Sources. - Never phrase an empty state as a fact about the world.
No usages found(still live inSpringCoreBundle) claims nothing exists; the code proved only that nothing was found in indexed project sources. The event-publisher key was fixed this way in #426:No publisher found in project sources. Assert the installed text withSpringGutterTestUtil.getGutterEmptyText. - Do not build the renderer/title inside a test to assert it. Assert through the wiring (see Algorithm step 6).
- Push feature branches to the
publicremote (explyt/spring-plugin); PRs target itsmain. Never push toorigin— it is an internal GitLab mirror. Use theghCLI with both--repo explyt/spring-pluginand--head <branch>, not the GitHub MCP tools.
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.
- 16d ago First seen · 98 lines · 142 tokens per session scan A daf50298f77d
develop-gutter-navigation-feature is a skill published in the GitHub repository explyt/spring-plugin (164 stars, last pushed today), licensed Apache-2.0. It adds 142 tokens to every session and 2,988 once invoked, about $0.0006 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-09-30.
Other skills, from other repositories
debug-rule
Debug a rule or approximation that behaves unexpectedly by tracing where taint is dropped. Use when its samples won't pass after repeated attempts, or it passes tests but is wrong on a real scan.
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.
report-analyzer-issue
Write a self-contained OpenTaint engine-issue report from an analysis diagnosis or a full-scan failure. Use when an engine-side issue needs a report.
write-fixture
Write Java/Kotlin tests with Fixture Monkey — enumerate the cases a method can produce, pick the ones worth testing, and build each fixture pinning only the properties that force the expected outcome.
test-hang-watchdog
Prevent and diagnose hanging or long-running Gradle unit tests (> 30s) in Android/Kotlin coroutines codebases. Use when running tests, when a test execution takes unexpectedly long, when background test tasks appear frozen, or when taking thread dumps (jstack) to unblock coroutine deadlocks.