What is spring-plugin AGENTS.md?

A contributor guide for Explyt Spring, an IntelliJ plugin that adds Spring, Quarkus, and JPA support to the IDE. It explains the Kotlin, Gradle, and multi-module project structure.

Use it when changing plugin modules, running the sandbox IDE, executing tests, building the plugin ZIP, or following the project's code and contribution conventions.

It shows where different features live and which commands build, test, run, and package the plugin.

How explyt/spring-plugin configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to explyt/spring-plugin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/explyt/spring-plugin/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/explyt/spring-plugin

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/explyt/spring-plugin/agents-md/github.svg)](https://agentmods.dev/instructions/explyt/spring-plugin/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/explyt/spring-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/explyt/spring-plugin/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/explyt/spring-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/explyt/spring-plugin/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,121 This file is loaded in full into every session.

When invoked 1,121 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01121	$0.01121
Opus 5.5	$0.00448	$0.00448
Sonnet 5.5	$0.00224	$0.00224
Haiku 4.5	$0.00112	$0.00112

Measured 20d ago against content hash 100f7d09c9c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spring-plugin AGENTS.md 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 20d 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.

AGENTS.md · 47 lines

How it starts

The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — Contributor Guide

Explyt Spring: a multi-module IntelliJ Platform plugin for Spring/Quarkus/JPA support. Kotlin 2.3.20, JDK 21, Gradle. Public open-source project (Apache-2.0): https://github.com/explyt/spring-plugin — issues, discussions, and PRs live there.

Project structure

modules/<name>/ — one Gradle module each, configured by modules/<name>/<name>.gradle.kts (not build.gradle.kts).
spring-core owns the bean model, inspections, navigation, properties, statistics — most changes land here. Feature modules (spring-web, spring-data, spring-security, …) match their names. base is Spring-agnostic shared utilities; test-framework holds test fixtures; spring-bootstrap is assembly-only (no feature code).
Sources: modules/<name>/src/main/kotlin/com/explyt/...; tests: src/test/kotlin; test data: modules/<name>/testdata/.
explyt-spring-boot-bean-reader/ is a separate Maven project (runtime javaagent for Native Context Mode).

Build, test, run

./gradlew :spring-bootstrap:runIde       # launch sandbox IDE (root runIde is disabled)
./gradlew :spring-bootstrap:buildPlugin  # ZIP → modules/spring-bootstrap/build/distributions/
./gradlew :spring-core:test              # one module's tests
./gradlew :spring-core:test --tests "com.explyt.spring.core.inspections.kotlin.SpringKotlinObjectInspectionTest"

Tests are IntelliJ Platform tests (headless IDE fixture) — slow and single-forked by design.

Code style and conventions

Kotlin-idiomatic code; match surrounding style. Every source file starts with the Apache-2.0 SPDX header Copyright (c) <year> Explyt Ltd, where <year> is the year the file is created; existing headers are not updated.
User-visible strings go through module message bundles (SpringCoreBundle, …); Spring FQNs come from constants holders like SpringCoreClasses.
IntelliJ threading rules apply: no slow work on EDT, PSI access under read/write actions, re-throw ProcessCanceledException, use SmartPsiElementPointer across async boundaries.
New inspections extend existing base classes (e.g. SpringBaseUastLocalInspectionTool), live in <module>/inspections/, and are registered in the module's plugin.xml. Reference pair: SpringKotlinObjectInspection.kt + its test.
Inspection tests use test-framework base classes (ExplytInspectionKotlinTestCase, …), declare libraries: Array<TestLibrary>, and usually have Java and Kotlin twins under inspections/java/ and inspections/kotlin/. Add or update tests for any behavior change.
Track new user-facing actions via StatisticActionId + StatisticService.addActionUsage(...).

Read the full file on GitHub · 47 lines

Changes

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.

20d ago Changed · +17 tokens per session 100f7d09c9c2
1mo ago Changed · +9 lines · +357 tokens per session 5e8e22c71d12
2mo ago First seen · 38 lines · 747 tokens per session scan A 43c8e11396db

Subscribe to this mod's changes

spring-plugin AGENTS.md is an instructions file published in the GitHub repository explyt/spring-plugin (166 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,121 tokens to every session, about $0.0045 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.

Java Testing ide kotlin plugin spring spring-boot

vibetags com-example-service-NewAnnotationsShowcase-SandboxTestHelper.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for sandboxtesthelper and sandbox restriction.

PIsberg/vibetags · 98 tokens

vibetags com-example-testing-PaymentFixturesTest.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for paymentfixturestest and context & focus.

PIsberg/vibetags · 91 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

spring-plugin: Instructions file for Codex