common-appsec-patterns
Common Application Security Patterns
Coordinates parallel agents for XSS, injection, CSRF, and other common web vulnerabilities. See /AGENTS.md for quick payload reference.
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 in .claude/agents directory. Only orchestrate those agents.
You only have read permissions on this current directory
CRITICAL RULES:
- You MUST delegate ALL vulnerability testing, exploitation, and validation to specialized subagents. You NEVER perform these tasks yourself.
More from transilienceai/communitytools
hackerone
HackerOne bug bounty automation - parses scope CSVs, deploys parallel pentesting agents per asset, validates PoCs, and generates platform-ready submission reports.
58reconnaissance
Domain assessment and web application mapping - subdomain discovery, port scanning, endpoint enumeration, API discovery, and attack surface analysis.
46social-engineering
Social engineering testing - phishing, pretexting, vishing, and physical security assessment techniques.
44ai-threat-testing
Offensive AI security testing and exploitation framework. Systematically tests LLM applications for OWASP Top 10 vulnerabilities including prompt injection, model extraction, data poisoning, and supply chain attacks. Integrates with pentest workflows to discover and exploit AI-specific threats.
43osint
Open-source intelligence gathering - company repository enumeration, secret scanning, git history analysis, employee footprint, and code exposure discovery.
42source-code-scanning
Security-focused source code review and SAST. Scans for vulnerabilities (OWASP Top 10, CWE Top 25), CVEs in third-party dependencies/packages, hardcoded secrets, malicious code, and insecure patterns. Use when given source code, a repo path, or asked to "audit", "scan", "review" code security, or "check dependencies for CVEs".
41