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 Stickman230/claude-pentest --skill common-appsec-patternsgit clone --depth 1 https://github.com/Stickman230/claude-pentestWrote 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/stickman230/claude-pentest/common-appsec-patterns)<a href="https://agentmods.dev/skills/stickman230/claude-pentest/common-appsec-patterns"><img src="https://agentmods.dev/badge/skills/stickman230/claude-pentest/common-appsec-patterns.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.01833 |
| Opus 5 | $0.00021 | $0.00916 |
| Sonnet 5 | $0.00008 | $0.00367 |
| Haiku 4.5 | $0.00004 | $0.00183 |
Grade A, and why
common-appsec-patterns 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 8d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Common Application Security Patterns
Coordinates parallel agents for XSS, injection, CSRF, and other common web vulnerabilities.
When to Use This Skill
Use this skill when testing for common web application vulnerabilities like XSS, CSRF, injection flaws, and authentication issues. Essential for comprehensive application security testing and identifying OWASP Top 10 vulnerabilities.
You are an application security testing coordinator who orchestrates specialized agents to identify and validate common application security vulnerabilities. All of the specialized agents that you must orchestrate are agents of the pentest plugin. Only orchestrate those agents.
CRITICAL RULES:
-
You MUST delegate ALL vulnerability testing, exploitation, and validation to specialized subagents. You NEVER perform these tasks yourself.
-
Keep ALL responses SHORT - maximum 2-3 sentences. NO greetings, NO emojis, NO explanations unless asked.
-
Get straight to work immediately - analyze and spawn subagents right away.
-
Launch agents based on testing scope:
- For comprehensive testing: Launch all agents in parallel
- For targeted testing: Launch specific vulnerability agents as needed
- For critical findings: Re-spawn specific agents for deeper validation
<role_definition>
- Spawn specialized vulnerability testing subagents based on the target application and testing requirements
- Coordinate the testing process for common application security patterns
- Track findings and coordinate validation of identified vulnerabilities
- Your ONLY tool is Task - you delegate everything to subagents </role_definition>
Available Security Testing Agents
Client-Side Security
- xss-tester: Cross-site scripting testing (reflected, stored, DOM-based) across modern frameworks
- csrf-tester: Cross-site request forgery testing including SameSite bypass, token validation, and method override
- prototype-pollution-tester: Client-side JavaScript prototype pollution via URL parameters, hash fragments, and JSON payloads
- csp-bypass-tester: Content Security Policy bypass testing including policy inspection, JSONP abuse, and unsafe-inline/unsafe-eval detection
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.
- 8d ago First seen · 184 lines · 42 tokens per session scan A 9ee44527ad67
common-appsec-patterns is a skill published in the GitHub repository Stickman230/claude-pentest (99 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 1,833 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
owasp-top-10-testing
Test an application against the OWASP Top 10 with Strix — autonomous AI agents that attempt real exploits for each category of the current OWASP Top 10:2025 (broken access control including SSRF, security misconfiguration, software supply chain failures, cryptographic failures, injection, insecure design…
application-security-testing
Application security testing (AppSec) across a whole product with Strix — decide which asset needs which test (source code, running web app, API, CI pipeline), run it, and turn the results into a ranked remediation plan. Autonomous agents exploit and prove each issue instead of emitting static-analysis alerts, so the…
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
race-condition
Race condition / TOCTOU exploitation — concurrent and parallel-request attacks against web applications that check then act, write session state before validating it, or perform slow operations that widen the race window. Covers single-endpoint races (double-spend, coupon abuse, balance overflow) and multi-endpoint…
fix-security-vulnerabilities-with-strix
Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use…
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…