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 RedHatProductSecurity/prodsec-skills --skill web-application-securitygit clone --depth 1 https://github.com/RedHatProductSecurity/prodsec-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/redhatproductsecurity/prodsec-skills/web-application-security)<a href="https://agentmods.dev/skills/redhatproductsecurity/prodsec-skills/web-application-security"><img src="https://agentmods.dev/badge/skills/redhatproductsecurity/prodsec-skills/web-application-security.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.00042 | $0.00977 |
| Opus 5 | $0.00021 | $0.00489 |
| Sonnet 5 | $0.00008 | $0.00195 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
web-application-security 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 7d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Application Security
Vulnerability Classes
| Category | Threats |
|---|---|
| Input validation | Command injection, SQL injection, Cross-Site Scripting (XSS) |
| Upload handling | Local File Inclusion (LFI), Remote File Inclusion (RFI) |
| Session management | Man-in-the-Middle (MITM), session fixation, session hijacking |
| Data exposure | Cleartext data theft, insecure storage, cache leaks |
| Authentication | Credential stuffing, brute force, account enumeration |
| Access control | Privilege escalation, IDOR, missing function-level checks |
Security Requirements
Server-Side Controls
All security controls MUST be implemented server-side. Client-side validation is a UX convenience, not a security boundary. This applies to:
- Input validation and sanitization
- Upload type and size restrictions
- Authentication and session management
- Authorization decisions
Network-Level Protections
- Deploy a Web Application Firewall (WAF) in front of public-facing applications where feasible
- Enable DDoS protection on Internet-facing endpoints
- Terminate TLS at the edge; enforce HTTPS end-to-end
CORS
- Configure Cross-Origin Resource Sharing to allow only known, explicitly listed origins
- Never use wildcard (
*) origins on endpoints that accept credentials - Validate the
Originheader server-side before reflecting it
CSRF Protection
- Enable framework-provided CSRF token mechanisms (e.g., Django CSRF middleware, Spring CSRF, Rails
protect_from_forgery) - Use
SameSitecookie attributes as a defense-in-depth layer - Verify tokens on every state-changing request
Session Management
- Generate a new session ID after successful authentication (prevent session fixation)
- Never expose session IDs in URLs
- Store session tokens in secure, HttpOnly, SameSite cookies
- Invalidate sessions on logout, idle timeout, and absolute timeout
- Bind sessions to client fingerprint where feasible (IP, User-Agent)
Sensitive Data Handling
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.
- 7d ago First seen · 102 lines · 42 tokens per session scan A 4472938e3da4
web-application-security is a skill published in the GitHub repository RedHatProductSecurity/prodsec-skills (52 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 977 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…