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.
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 agentmods add skills/apache/struts/creating-version-notesnpx skills add apache/struts --skill creating-version-notesgit 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/creating-version-notes)<a href="https://agentmods.dev/skills/apache/struts/creating-version-notes"><img src="https://agentmods.dev/badge/skills/apache/struts/creating-version-notes.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 | $0.00064 | $0.05320 |
| Opus 5 | $0.00032 | $0.02660 |
| Sonnet 5 | $0.00013 | $0.01064 |
| Haiku 4.5 | $0.00006 | $0.00532 |
Grade A, and why
creating-version-notes 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 yesterday.
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 — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Version Notes
Overview
A Version Notes page answers one question for a user deciding whether to upgrade: what changed in this release, and what will break. Almost all of it is a mechanical rendering of a JIRA fix version onto fixed boilerplate.
Core principle: the mechanical parts must be derived, never retyped; the two judgement parts — Breaking changes, and how a security fix is described — are the only places you author prose.
One skill covers every maintenance line. 6.x and 7.x pages share an identical structure. The line changes the data (version, prior page, JIRA ids), never the process.
This is phase 3 of a seven-phase release. releasing-struts holds the sequence, the gates and the mechanics either side of it; this skill owns the paperwork.
The Iron Rule
START FROM THE TEMPLATE. NEVER CLONE THE PREVIOUS VERSION NOTES PAGE.
Cloning is how the published pages acquired their defects, and it fails differently every time:
| Page | Inherited defect |
|---|---|
| Version Notes 6.9.0 | Issue Detail links "JIRA Release Notes 6.8.0" — label and version= id both from 6.8.0 |
| Version Notes 6.10.0 | Issue List links "Struts 6.9.0 DONE" — label names the previous release, against a filter= id different from the one the 6.9.0 page used |
| Both series | Maven Dependency code macro carries ac:name="" instead of ac:name="language" |
Half-updated links are the signature failure: the number gets fixed and the label doesn't, or the reverse. They survive review because the link still works — it just points at, or claims to be, the wrong release.
version-notes-template.md is the source of truth: field guidance, storage-format skeleton with those defects corrected, and the pre-publication checklist.
Collect every input before writing
Each row is derived from a named source. A value you cannot source is a visible placeholder, never a guess.
| Input | Where it comes from |
|---|---|
| Version | The release being voted or announced |
| Parent page | Always Migration Guide (page id 13981) — every Version Notes page is a child of it |
| Prior notes page title | The previous released version in the same series — see below |
| JIRA version id | Numeric id behind ReleaseNote.jspa?version= — from the WW project's versions, not the version name |
| DONE filter id | The saved JIRA filter for this release; a new release needs a new filter |
| Issue list | project = WW AND fixVersion = <version>, grouped by type |
| Breaking changes | Authored — see below |
| Staging Repository block | An explicit decision — see below |
What ships with it
1 file 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.
- yesterday First seen · 330 lines · 64 tokens per session scan A 592530bc0c54
creating-version-notes is a skill published in the GitHub repository apache/struts (1,366 stars, last pushed yesterday), licensed Apache-2.0. It adds 64 tokens to every session and 5,320 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
update-site-for-release
Update/publish the Apache Tika website (tika-site SVN repo) for a release — step 17 of the Release Process. Handles the 4.x track (Changes page + aggregate javadoc + Antora docs branch) vs the 3.x maintenance track (full per-version apt docs + javadoc). Use for "update the site", "publish the site for X.Y.Z", "the…
release-sample-sweep
Run the pre-release end-to-end sweep of every user-facing surface — the 33 samples under samples/ (booted from their packaged artifacts and driven in a real browser via chrome-devtools MCP), the Expo/React Native client, and the atmosphere CLI. Use before cutting a release, and after any change to the Console bundle…
release-plugin
Prepare and execute a new release for the flutter-intellij plugin, including updating dependencies, compatibility bounds, changelogs, and verification.
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…
babysit-pr
Shepherd one or more camunda/camunda PRs through flaky CI and the merge queue to merged. Accepts a list of PRs (e.g. a merge plus its backports). Use when asked to babysit, shepherd, watch, drive, or "get merged" one or more PRs, or to keep retrying CI until they land.
changelog-release-notes
BK-CI 发版 Changelog 增量处理：仅针对本次新增版本块生成「变更概述」并写回中文文件， 再将该增量版本翻译到英文 CHANGELOG。当用户提到发版摘要、变更概述、CHANGELOG 翻译、 中英文 changelog、vX.Y.Z-rc、补充概述、同步英文日志时使用。.