security-auditor
Skill1 starsChanged 9 months agoMITView on GitHub
Comprehensive security analysis against OWASP Top 10 standards. Use after code-reviewer for code handling: authentication, user input, database queries, external APIs.
57 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- MonkeyNull/security-auditortheir own version, first seen Nov 15, 2026
- swap-cameroon/kuro-antigravity-configtheir own version, first seen Nov 15, 2026
- letscooktech-studio/ai-engineering-arsenaltheir own version, first seen Nov 8, 2026
- letscooktech-studio/outcomelabtheir own version, first seen Nov 8, 2026
- raphaeltm/simple-agent-managertheir own version, first seen Nov 7, 2026
- omspradippatil/Claude-Skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use proofreader, refactoring-guide and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
xcrrrSkillproofreader
Use this skill when reviewing written content for grammar, spelling, punctuation, style consistency, and tone—before publishing, submitting, or sending. Trigger phrases: 'proofread this', 'check my writing', 'review this for errors', 'edit this email/report/essay'. Do NOT use when structural rewrites or content changes are needed—proofreading fixes surface errors, not substantive problems.
Also in 3 projects that use this
peopleforresterSkillrefactoring-guide
Safe refactoring patterns and techniques. Use when the user wants to improve code structure, reduce duplication, or make code more maintainable without changing behavior. Emphasizes incremental changes with test coverage.
Also in 3 projects that use this
zwjbendnSkillhabit-builder
Designs and manages healthy habits for sustainable weight loss through lifestyle change. Uses Atomic Habits / Tiny Habits methodology — small behaviors that compound over time. Use this skill when: the system needs to recommend a new habit after onboarding, a current habit graduates or fails, the user asks about building habits, or Weekly Review identifies a behavioral pattern worth addressing. Also use when evaluating habit progress, deciding when a habit has "graduated," or handling a restart after the user falls off. This skill does not send its own reminders — habit check-ins are woven into meal conversations managed by Notification Composer. This skill owns the check-in logic (when, how often, tone); Notification Composer provides the conversation vehicle.
Also in 3 projects that use this
juanlurgSkillsql-optimizer
Analyzes SQL queries and generates an optimization report notebook with explanations, identified issues, and rewritten queries. Use when the user wants to optimize, explain, improve, or debug a SQL query, or mentions query performance, slow queries, or SQL optimization.
Also in 3 projects that use this
belokonmSkilldata-scientist
Expert in statistical analysis, predictive modeling, machine learning, and data storytelling to drive business insights.
Also in 3 projects that use this
glinckerSkillqa-engineer
QA specialist agent for test planning, execution, and regression analysis
Also in 3 projects that use this
Other versions57 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- stepanenkoviktor0110-boop/ai-dev-methodology★ 272% same
Wrote their own version · 56
- pavel-molyanov/molyanov-ai-dev★ 299same name
- dralgorhythm/claude-agentic-framework★ 118same name
- nahisaho/MUSUBI★ 74same name
- raphaeltm/simple-agent-manager★ 69same name
- amanning3390/hermeshub★ 48same name
- jshsakura/awesome-opencode-skills★ 30same name
- Fandry96/k3-agentic-skills★ 27same name
- jaskirat1616/grok-skills★ 22same name
- mrhinkle/VibeCoding-a-Website★ 17same name
- jshearin01/agent-skills★ 16same name
46 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- skills/skill-master/references/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- code-reviewingSkill
- code-writingSkill
- deploy-pipelineSkill
- documentation-writingSkill
- feature-executionSkill
- infrastructure-setupSkill
- methodologySkill
- post-deploy-qaSkill
- pre-deploy-qaSkill
- project-planningSkill
- prompt-masterSkill
- skill-masterSkill
- skill-test-designerSkill
- skill-testerSkill
- task-decompositionSkill
- tech-spec-planningSkill
- test-masterSkill
- user-spec-planningSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 50 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 55
If any missing, request them before proceeding.
- Distinctive: line 60
Check auth at each protected endpoint
- Distinctive: line 64
Verify security headers and CORS policies
- Distinctive: line 65
Run dependency vulnerability scans
- Distinctive: line 71
Avoid false positives by understanding full context
- Distinctive: line 72
Consider defense-in-depth already in place
- Distinctive: line 76
Thorough But Precise: No false positives, no missed real vulnerabilities
- Distinctive: line 77
Context Matters: Consider full application context
- Distinctive: line 78
Prioritize Actionability: Every finding must have implementable fix
- Distinctive: line 82
Dependencies First: Always include npm audit results
“Common” is measured: kept by at least 6 in 10 of the 50 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Security Auditor
Elite security analysis with deep expertise in OWASP Top 10 and modern vulnerability assessment.
Core Responsibilities
- Comprehensive Security Analysis:
- SQL Injection (parameterized queries, ORM usage, raw SQL)
- Cross-Site Scripting (XSS) - stored, reflected, DOM-based
- Cross-Site Request Forgery (CSRF) protection
- Authentication (password storage, session management, MFA)
- Authorization and access control (RBAC, ABAC, privilege escalation)
- Input validation and sanitization (server-side validation, type checking)
- Cryptography (algorithms, key management, secure random)
- Dependency vulnerabilities (npm audit, outdated packages, CVEs)
- Rate limiting and DoS protection
- CORS configuration
- Security headers (CSP, HSTS, X-Frame-Options)
- Hardcoded secrets (API keys, tokens, passwords, connection strings in source code)
- SSRF (server-side request forgery — user-controlled URLs in server-side requests)
- Insecure design (missing threat modeling, business logic flaws)
- Software and data integrity (deserialization attacks, CI/CD integrity)
- Security logging and monitoring (audit trails, security event logging)
- Risk Assessment - Classify by severity:
- Critical: Immediate exploitation, severe impact (data breach, RCE)
- High: Significant risk requiring urgent attention (auth bypass, injection)
- Medium: Notable concerns needing timely fixes (weak crypto, missing headers)
- Low: Best practice violations (information disclosure)
- Dependency Analysis: npm audit (or equivalent), analyze:
- Direct and transitive dependency vulnerabilities
- Outdated packages with known security issues
- Recommended upgrade paths
Operational Protocol
Input Requirements:
- List of files to audit
- User specifications (requirements, expected functionality)
- Technical specifications (architecture, frameworks, dependencies)
If any missing, request them before proceeding.
Analysis Methodology:
- Review files systematically, starting with entry points (routes, controllers)
- Trace data flow from input to output, identifying trust boundaries
- Check auth at each protected endpoint
- Examine all database queries for injection
- Analyze user input handling and output encoding
- Review cryptographic implementations
- Verify security headers and CORS policies
- Run dependency vulnerability scans
- Cross-reference with OWASP Top 10
Quality Assurance:
- Provide specific line numbers and code snippets
- Explain attack vector and potential impact
- Avoid false positives by understanding full context
- Consider defense-in-depth already in place
Guidelines
- Thorough But Precise: No false positives, no missed real vulnerabilities
- Context Matters: Consider full application context
- Prioritize Actionability: Every finding must have implementable fix
- Stay Current: Reference OWASP Top 10 (2021+) and current CVE databases
- Explain Impact: Make risks concrete with realistic attack scenarios
- Provide Examples: Include secure code in recommendations
- Dependencies First: Always include npm audit results
- No Assumptions: Flag uncertain framework protections for manual review
Escalation
Flag immediately:
- Critical vulnerabilities in production
- Signs of existing compromise or malicious code
- Systemic architecture issues requiring redesign
- Compliance violations (GDPR, PCI-DSS)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

