Apache Struts is an open-source Java web framework that helps developers build applications using the Model-View-Controller pattern, separating data and business logic from page presentation and request handling. Java developers use it to create dynamic web applications with interactive forms and database-backed behavior. The catalogue's skills, instructions, and setting support work with Struts projects.
Borrowing it
Nothing to install: this file belongs to apache/struts. 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/apache/struts/main/.claude/skills/merging-dependabot-prs/SKILL.mdgit clone --depth 1 https://github.com/apache/strutsWrote 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/apache/struts/merging-dependabot-prs)<a href="https://agentmods.dev/skills/apache/struts/merging-dependabot-prs"><img src="https://agentmods.dev/badge/skills/apache/struts/merging-dependabot-prs/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/apache/struts/merging-dependabot-prs"><img src="https://agentmods.dev/badge/skills/apache/struts/merging-dependabot-prs.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.00052 | $0.02757 |
| Opus 5.5 | $0.00021 | $0.01103 |
| Sonnet 5.5 | $0.00010 | $0.00551 |
| Haiku 4.5 | $0.00005 | $0.00276 |
Grade A, and why
merging-dependabot-prs 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 19d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merging Dependabot PRs
Overview
Dependabot opens bumps against main and support/struts-6-x-x. Most land as-is.
A bump that ships to users needs a WW Jira ticket first, and the ticket ID must
reach the PR title, the PR body and the squash commit subject before it merges.
Core principle: the decision is driven by the dependency's real Maven scope, not by
what Dependabot calls it. Dependabot's build(deps-dev): prefix and its
dependency-type: trailer are guesses about its own ecosystem, not this project's
POM. Read the POM.
The decision
Read the semver class from the Dependabot commit trailer — never parse version strings:
gh pr view <N> --json commits --jq '.commits[].messageBody' \
| grep -E 'dependency-name:|update-type:'
# update-type: version-update:semver-{patch|minor|major}
Then find the real scope, and cross the two:
| What is being bumped | patch | minor | major |
|---|---|---|---|
GitHub Action (.github/workflows/*) |
merge bare | merge bare | merge bare |
Maven plugin or build tooling (<build><plugins>, *-maven-plugin, maven-wrapper) |
merge bare | merge bare | merge bare |
Maven dep, <scope>test</scope> |
merge bare | merge bare | merge bare |
Maven dep in apps/ (showcase, rest-showcase) |
merge bare | merge bare | merge bare |
Maven dep, compile / runtime / provided — including <optional>true</optional> |
merge bare | TICKET | TICKET |
"Merge bare" always still requires a green build (see below).
Finding the real scope
grep -rn '<artifactId>NAME</artifactId>' --include=pom.xml . | grep -v /target/
Read the <scope> on the surrounding <dependency> block in the module that declares it
(core/pom.xml, plugins/*/pom.xml), not the <dependencyManagement> copy in
parent/pom.xml — the managed block usually carries no scope.
- No
<scope>element means compile — it ships. <optional>true</optional>still ships: it is published in the module's POM and users who opt in inherit the version. Optional is not exempt.- For a version property (
jackson.version,byte-buddy.version), resolve the property to the artifacts it feeds and take the widest scope among them.
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.
- 19d ago Changed · +16 lines 923d3ff031d0
- 24d ago Changed · +1 lines 8f8961ef2584
- 1mo ago First seen · 205 lines · 52 tokens per session scan A 301f56008e78
merging-dependabot-prs is a skill published in the GitHub repository apache/struts (1,371 stars, last pushed 2d ago), licensed Apache-2.0. It adds 52 tokens to every session and 2,757 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-09-03.
Other skills, from other repositories
kanban
Use when work has several deliverables, tickets, or delegates: board, WIP 1 writer + 2 review, pull rule, Definition of Done, findings fixed or filed.
pre-done-self-review
Use before claiming Done, signing off, or handing off: reconcile every item with all standing rules, cite rule and alternative for each gap, check views. On demand only.
110-java-maven-best-practices
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should…
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
spring-plugin-issue-delivery
Orchestrates explyt/spring-plugin GitHub issues end to end by routing work to Test, Code, Review and Ask agents and forks: one writer per checkout, parallel lanes in sibling git worktrees, stacked PRs for dependent work, briefs, verification of every returned result, PR split and merge order, refreshing open PRs after…
enterprise-maven-pom
Dasel v3 selector patterns for Maven POM XML files — use when querying dependency versions, filtering by groupId or scope, extracting module hierarchy from parent POMs, or detecting version conflicts across enterprise multi-module Java projects. Load this skill when working with pom.xml files using dasel.