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-security-bulletinsnpx skills add apache/struts --skill creating-security-bulletinsgit 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-security-bulletins)<a href="https://agentmods.dev/skills/apache/struts/creating-security-bulletins"><img src="https://agentmods.dev/badge/skills/apache/struts/creating-security-bulletins.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.00066 | $0.05354 |
| Opus 5 | $0.00033 | $0.02677 |
| Sonnet 5 | $0.00013 | $0.01071 |
| Haiku 4.5 | $0.00007 | $0.00535 |
Grade A, and why
creating-security-bulletins scanned grade A with 1 finding 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.
Unrestricted tool accesslowExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
| **Critical** | A remote attacker can get Struts to execute arbitrary code — exploitable automatically, regardless of whether the developer followed the Security Guide | Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Security Bulletins
Overview
An S2-XXX bulletin exists to tell an operator what to upgrade and why — not to explain the defect. Every sentence that helps a defender must be weighed against how much it helps someone building an exploit.
Core principle: every field is either traced to source you read this session, or a visible placeholder. Never a plausible guess.
Process authority: SECURITY.md governs disclosure. This skill governs what the page says and how it is written.
REQUIRED BACKGROUND: the claims you put in a bulletin come from triage. Use triaging-security-reports to establish them before writing.
The Iron Rule
NO FIELD IN A BULLETIN WITHOUT A SOURCE YOU READ THIS SESSION,
OR A VISIBLE PLACEHOLDER.
Applies to the severity rating, the affected versions, and above all the Workaround. "There is no workaround" is a factual claim about absence — the hardest kind to get right, and the most common thing to assert without checking.
Page structure
Sections in order, matching the existing published bulletins:
Summary (in an excerpt macro) → field table → Problem → Solution → Backward compatibility → Workaround
Field table rows, in order:
| Row | Content |
|---|---|
| Who should read this | Usually All Struts 2 developers and users; narrow it only when exposure is genuinely conditional |
| Impact of vulnerability | A short impact phrase, not a paragraph — Remote Code Execution, Denial of service, Disclosure of Data, Denial of Service, Server Side Request Forgery. Hedging is accepted where warranted (Possible Remote Code Execution vulnerability) |
| Maximum security rating | Low / Moderate / Important / Critical — see the rating scale below |
| Recommendation | Upgrade to Struts X.Y.Z at least. Name every maintenance line that carries the fix (Upgrade to Struts 6.8.0 or 7.1.1 at least), and add the required action where upgrading alone is not enough (… and use Action File Upload Interceptor) |
| Affected Software | Officially released versions only (see below); bullet one range per maintenance line, linking the EOL announcement for end-of-life ranges |
| Reporters | Credit the reporter — they earned it, and it costs nothing. Include their organisation where they gave one (Steven Seeley of Source Incite); obfuscate any email (pwntester at github dot com) |
| CVE Identifier | Placeholder until assigned (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 · 301 lines · 66 tokens per session scan A 6ff5b1ea412d
creating-security-bulletins is a skill published in the GitHub repository apache/struts (1,366 stars, last pushed yesterday), licensed Apache-2.0. It adds 66 tokens to every session and 5,354 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
azure-security-keyvault-secrets-java
Azure Key Vault Secrets Java SDK for secret management. Use when storing, retrieving, or managing passwords, API keys, connection strings, or other sensitive configuration data.
azure-ai-anomalydetector-java
Build anomaly detection applications with Azure AI Anomaly Detector SDK for Java. Use when implementing univariate/multivariate anomaly detection, time-series analysis, or AI-powered monitoring.
azure-communication-chat-java
Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time chat features.
union-type-wrappers
Add typed getters and setters over BinaryData properties that represent TypeSpec union types in generated Java models. Use when generated classes expose BinaryData for union-typed fields and you need ergonomic, type-safe accessors instead.
azure-ai-agents-persistent-java
Azure AI Agents Persistent SDK for Java. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Triggers: "PersistentAgentsClient", "persistent agents java", "agent threads java", "agent runs java", "streaming agents java".