Borrowing it
Nothing to install: this file belongs to solacecommunity/spring-solace-leader-election. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/solacecommunity/spring-solace-leader-election/master/.agents/skills/dependency-update/SKILL.mdgit clone --depth 1 https://github.com/solacecommunity/spring-solace-leader-electionWrote 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/solacecommunity/spring-solace-leader-election/dependency-update)<a href="https://agentmods.dev/skills/solacecommunity/spring-solace-leader-election/dependency-update"><img src="https://agentmods.dev/badge/skills/solacecommunity/spring-solace-leader-election/dependency-update/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/solacecommunity/spring-solace-leader-election/dependency-update"><img src="https://agentmods.dev/badge/skills/solacecommunity/spring-solace-leader-election/dependency-update.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.00041 | $0.00702 |
| Opus 5.5 | $0.00016 | $0.00281 |
| Sonnet 5.5 | $0.00008 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
dependency-update 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 27d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Update Workflow
When to Use
- Periodic dependency freshness check
- After Dependabot PRs to verify compatibility
- Before a release to ensure all dependencies are current
- When upgrading Spring Boot or Spring Cloud versions
Procedure
Step 1: Analyze Current Dependencies
Read pom.xml and catalog all dependencies AND plugins with explicit versions vs BOM-managed versions.
Always update to the latest stable version listed on Maven Central.
Key explicitly-versioned dependencies to check:
spring-boot-starter-solace-client-configmicrometer-bomaspectjrt/aspectjweavertestcontainers-solace- All Maven plugins with explicit versions
Step 2: Check for Updates
For each explicitly-versioned dependency and plugin:
- Check Maven Central for the latest stable release via web search (skip RC/alpha/beta)
- Only update if the version is actually available and downloadable from Maven Central
- Verify compatibility with the current Spring Boot and Spring Cloud BOMs
- Assess risk level: patch (safe), minor (review changelog), major (breaking — review carefully)
Step 3: Apply Updates
For approved updates:
- Update the version in
pom.xml - Run build verification:
Note: Usemvn verify "-Dgpg.skip" -DskipTests-Dgpg.skipbecause GPG signing is not available in dev environments. - If build succeeds, run tests:
mvn test > maven_tests.log 2>&1 - If tests pass, run integration tests:
mvn verify > maven_it_tests.log 2>&1 - Parse results:
tail -20 maven_tests.logandgrep -E "Tests run:|BUILD" maven_tests.log
Step 4: Version Bump
After successful mvn verify, bump the project version to the next patch release:
- Update
<version>inpom.xml(e.g. 2.0.1 → 2.0.2) - Update the Maven dependency snippet in
README.mdto the new version
Step 5: Update Documentation
README.md — Version Compatibility Table
- Only ADD a new line at the top of the table for the new version
- NEVER modify or replace existing lines in the table — they are historical records
- Update the Maven dependency snippet
<version>to the new version
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.
- 27d ago First seen · 76 lines · 41 tokens per session scan A 2e0c0038450a
dependency-update is a skill published in the GitHub repository solacecommunity/spring-solace-leader-election (4 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 702 once invoked, about $0.0002 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-10-02.
Other skills, from other repositories
senior-java
World-class Java and Spring Boot development skill for enterprise applications, microservices, and cloud-native systems. Expertise in Spring Framework, Spring Boot 3.x, Spring Cloud, JPA/Hibernate, and reactive programming with WebFlux. Includes project scaffolding, dependency management, security implementation, and…
creating-springboot-projects
Use when starting a new Spring Boot project or service: scaffolding or bootstrapping a backend, REST API, microservice or modular monolith; choosing how to structure it (layered, package-by-module, modular monolith, tomato, DDD-hexagonal); selecting Spring Boot 4 features; generating the base project with progen or…
springboot-migration
Use when upgrading an existing Spring Boot application, for example from Boot 3.x to Boot 4 or to the latest Spring Boot and Java: dependency transitions and starter renames, test annotations such as @MockBean to @MockitoBean, Jackson 3 issues, Spring Modulith 2 or Testcontainers 2 upgrades, code that stops compiling…
aws-sdk-java-v2-bedrock
Provides Amazon Bedrock patterns using AWS SDK for Java 2.x. Invokes foundation models (Claude, Llama, Titan), generates text and images, creates embeddings for RAG, streams real-time responses, and configures Spring Boot integration. Use when asking about Bedrock integration, Java SDK for AI models, AWS generative…
aws-lambda-java-integration
Provides AWS Lambda integration patterns for Java with cold start optimization. Use when deploying Java functions to AWS Lambda, choosing between Micronaut and Raw Java approaches, optimizing cold starts below 1 second, configuring API Gateway or ALB integration, or implementing serverless Java applications. Triggers…
langchain4j-ai-services-patterns
Provides patterns to build declarative AI Services with LangChain4j for LLM integration, chatbot development, AI agent implementation, and conversational AI in Java. Generates type-safe AI services using interface-based patterns, annotations, memory management, and tools integration. Use when creating AI-powered Java…