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 pledgeandgrow/pledge-skills --skill springgit clone --depth 1 https://github.com/pledgeandgrow/pledge-skillsWrote 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/pledgeandgrow/pledge-skills/spring)<a href="https://agentmods.dev/skills/pledgeandgrow/pledge-skills/spring"><img src="https://agentmods.dev/badge/skills/pledgeandgrow/pledge-skills/spring.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.1 | $0.00043 | $0.01366 |
| Opus 5 | $0.00022 | $0.00683 |
| Sonnet 5 | $0.00009 | $0.00273 |
| Haiku 4.5 | $0.00004 | $0.00137 |
Grade A, and why
spring-ecosystem-docs 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 8d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Framework Ecosystem
Overview
Spring is the most widely-used Java application framework for building enterprise applications. It provides comprehensive infrastructure support for developing Java applications, with a focus on inversion of control (IoC), dependency injection (DI), aspect-oriented programming (AOP), and modular project structure.
The Spring ecosystem consists of multiple projects that build on the Spring Framework core:
- Spring Boot - Stand-alone, production-grade applications with auto-configuration and embedded servers
- Spring Framework - Core IoC container, AOP, web MVC, WebFlux, data access, testing
- Spring Security - Authentication, authorization, OAuth2, CSRF, session management
- Spring Data - Repository abstractions for JPA, MongoDB, Redis, JDBC, REST, and more
Key Concepts
- Inversion of Control (IoC) - Objects define their dependencies through constructor arguments, factory methods, or setters; the container injects them
- Dependency Injection (DI) - The Spring container manages bean lifecycle and wires dependencies
- Beans - Objects managed by the Spring IoC container
- ApplicationContext - The central interface for configuration and bean management
- Auto-configuration - Spring Boot automatically configures beans based on classpath dependencies
- Starters - Opinionated dependency descriptors that simplify build configuration
- Actuator - Production-ready features: health checks, metrics, monitoring via HTTP/JMX
- Externalized Configuration - Properties/YAML files, environment variables, command-line args
- AOP - Cross-cutting concerns like transactions, logging, security via aspects
- Spring MVC - Servlet-stack web framework with annotation-based controllers
- Spring WebFlux - Reactive-stack web framework built on Reactor
- Repository abstraction - Spring Data's pattern for data access with minimal boilerplate
Project Structure
A typical Spring Boot application:
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 165 lines · 43 tokens per session scan A 5b567ec9288e
spring-ecosystem-docs is a skill published in the GitHub repository pledgeandgrow/pledge-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,366 once invoked, about $0.0002 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-31.
Other skills, from other repositories
spring-boot
Spring Boot 3.x - Java framework for production-ready applications with dependency injection, REST APIs, data access, security, and actuator monitoring.
spring-boot-patterns
A set of Spring Boot coding rules for Forge projects, including constructor-based dependency setup, typed application settings, and RFC 7807 error responses. Spring Boot is a framework for building Java and Kotlin web applications.
kotlin-backend-jpa-entity-mapping
Model Kotlin persistence code correctly for Spring Data JPA and Hibernate. Covers entity design, identity and equality, uniqueness constraints, relationships, fetch plans, and common ORM (Object-Relational Mapping) traps specific to Kotlin. Use when creating or reviewing JPA (Java Persistence API) entities, diagnosing…
plugin-code-review-orchestrated
Orchestrates a code review of the spring-plugin repository through scope/context passes, routing, domain reviewer subskills, and per-artifact validation. Use when asked to review a PR, diff, commit, branch, module, or file set, to run a full orchestrated review, or to produce a validated review report.
github-issue-manager
Classifies a user request as Bug, Compatibility, Feature, Question, or Task for the explyt/spring-plugin GitHub repo, lightly researches the relevant codebase, searches similar existing issues, and either reports an existing issue or creates a correctly titled and labeled one following the repository issue forms. Use…
review-async-lifecycle
Normative reviewer for EDT safety, coroutines, cancellation, read/write actions, disposal, listeners and async lifecycle in the explyt spring-plugin. Use during orchestrated code review when the diff touches threading, background tasks, read or write actions, listeners, MessageBus, Disposable ownership or progress…