eos-security
engineering-os/engineering-os/.agents/skills/eos-security/SKILL.md
Run adversarial Engineering OS security scanning, auditing, dependency checks, threat modeling, or compliance checks.
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
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.
engineering-os/engineering-os/.agents/skills/eos-security/SKILL.md
Run adversarial Engineering OS security scanning, auditing, dependency checks, threat modeling, or compliance checks.
muyen/vibe-to-prod/.claude/skills/security-scan/SKILL.md
Proactive security scanning. Triggers when modifying auth, API endpoints, user data, or sensitive operations.
Often used withdjango-securitydeployment-patternspostgres-patterns
fleetdm/fleet/.claude/skills/security-triage/SKILL.md
Use when a security report arrives or needs a reply - a new Bugbop report (VDP or private bug bounty), a GitHub security advisory submission in the "triage" state on fleetdm/fleet, a disclosure in the security inbox, a reporter asking "any update?", or a fix merging for a tracked report. Also use for the daily security report triage ritual.
Steady8 mentions in 2 weeks
24 projects use a version of this
getsentry/skills/skills/security-model/SKILL.md
Define, review, or update SECURITY_MODEL.md files that tell security review tools a repository's threat model, trust boundaries, invariants, reportable finding classes, and exclusions. Use when asked to "write a security model", "threat model this repo for scanners", "define security review scope", "what counts as a vulnerability here", "update SECURITY_MODEL.md", "why did the scanner flag or miss this", or to check whether existing security guidance still matches the code. Not for running a security review or editing the SECURITY.md disclosure policy.
joe-bell/cva/.agents/skills/security-review/SKILL.md
Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.
Steady5 mentions in 2 weeks
192 projects use a version of this
Often used withlinkerd-patternsdependency-cve-sweepproject-guidelines-example
bienhoang/wp-pro-max/skills/wp-security/SKILL.md
Hardens a WordPress build and scans it for vulnerabilities (stage `security`). Applies a hardening checklist via WP-CLI / wp-config (disable file editing, force SSL admin, security headers, limit login attempts, regenerate strong salts, file-permission guidance, hide version, disable XML-RPC if unused, least-privilege users) and runs a vulnerability scan of core/plugins/themes (wp core/plugin/theme check-update plus WPScan/Patchstack known-vuln lookup) and a secrets scan of the theme. Reports findings by severity. Use when hardening WordPress, applying security headers, scanning for vulnerable plugins/themes or leaked secrets, or when the pipeline reaches the `security` stage. Reuses the repo security-scan skill where available. Reads plugins, theme, project; writes security.{hardeningApplied,vulnScan}.
romangalaxys10-spec/fable/skills/qa-security/SKILL.md
name: qa-security title: Automated Security Testing & OWASP Hardening category: Security author: Principal QA Architect & Systems Staff Engineer --- # qa-security — Security Testing & OWASP Hardening Scans for security vulnerabilities including OWASP
thejordanleopold/claude-code-skills-distilled/ai-security/SKILL.md
Use when auditing AI/LLM systems for security vulnerabilities, reviewing prompt injection risks, auditing MCP server tool integrations, assessing AI agent behavioral drift, reviewing credential scoping for agents, or designing safe agentic systems. Triggers: \"AI security\", \"LLM security\", \"prompt injection\", \"tool abuse\", \"MCP security\", \"agent security\", \"behavioral drift\", \"AI agent audit\", \"insecure plugin\", \"agentic threat\", \"LLM threat\", \"indirect injection\", \"credential exposure\", \"excessive agency\".
2233admin/reverse-skill-evolver/skills/api-security/SKILL.md
Test authorized REST, GraphQL, WebSocket, and SOAP APIs for authentication, authorization, input validation, and rate-limiting flaws. Use for API security assessments and JWT/OAuth testing.
Often used withbinary-diffpentest-toolsllm-security
2233admin/reverse-skill-evolver/skills/llm-security/SKILL.md
Assess authorized LLM applications and AI agents for prompt injection, tool misuse, memory poisoning, and model supply-chain weaknesses. Use for AI application security testing and agent threat analysis.
Often used withattack-chainpentest-toolsbinary-diff
duriantaco/skylos/.agents/skills/skylos-security/SKILL.md
Investigate and harden Skylos security behavior. Use when the user asks to validate a security finding, reproduce a scanner bypass, assess false negatives, review LLM evidence filters, analyze CI/cloud policy trust boundaries, classify severity, or add regression tests for security-sensitive analyzer behavior.
5throck/ai-workspace-standards/.agents/skills/security-scan/SKILL.md
Runs static analysis, secret detection (via gitleaks), dependency vulnerability auditing (via bun audit), and auth-surface auditing (unauthenticated signup endpoints) across the workspace.
Often used withdjango-securitydeployment-patternspostgres-patterns
doorkeeper-gem/doorkeeper/.agents/skills/security-review/SKILL.md
Verify that code changes do not introduce OAuth security vulnerabilities. Use when modifying token handling, client authentication, scope validation, redirect URI checks, secret comparison, or grant flows in Doorkeeper.
Often used withlinkerd-patternsdependency-cve-sweepproject-guidelines-example
laolaoshiren/claude-code-skills-zh/skills/security-audit/SKILL.md
代码安全审计 - 漏洞扫描、依赖检查、安全最佳实践
Often used withcreate-storiescommunity-led-growthstory-done
nirholas/pump-fun-sdk/skills/pump-security/SKILL.md
Defense-in-depth security across Rust, TypeScript, and Bash for the Pump SDK — cryptographic key handling, memory zeroization, secure file I/O, input validation, privilege management, dependency auditing, and a 60+ item security checklist.
rack/rack/.agents/skills/security-triage/SKILL.md
End-to-end process for handling a Rack security report (GitHub Security Advisory) from receipt to backported release. Use when asked to triage, review, accept, describe, fix, merge, or backport a security advisory, or to review a review document for one.
skyelan1999/aide/.agents/skills/aide-security/SKILL.md
Review or implement Aide authentication, permissions, tokens, secrets, path safety, encryption, or other security-sensitive behavior.
RustNSparks/sockudo/.agents/skills/security-audit/SKILL.md
Security audit of a codebase — web apps, APIs, services, CLI tools, libraries, daemons, and more. Use when asked to find security bugs, do a security review, audit for vulnerabilities, or pen-test the code. Focuses on exploitable issues with real impact, not theoretical concerns or industry-standard behavior.
Often used withcreate-storiescommunity-led-growthstory-done
dithiothreitol/ea-skills/skills/ea-security/SKILL.md
Work the security architecture in the existing model - classify data, mark exposure and trust zones, find unguarded paths from the public internet, propose threat assessments for trust-boundary crossings, anchor high-rated systems to a control framework (NIST SP 800-53, SP 800-207, CSF), and check SBOMs against security standards. Use for security architecture reviews, threat modelling, attack-surface or "what could an attacker reach" questions, data classification, zero-trust or control-coverage questions, and SEC001-SEC003 or ALN009 findings.
Kin9Zeus/senior-engineer-skills/skills/ai-security/SKILL.md
Security for AI-powered software — LLM applications, agents, tool calling, RAG, MCP servers and AI-assisted coding. Covers prompt injection (direct and indirect), excessive agency, output handling, data leakage, vector-store tenant isolation, AI-provider key theft and spend abuse, supply chain for models, plugins and skills, and testing and monitoring of AI features. Use when the user says "prompt injection", "jailbreak", "secure my chatbot", "LLM security", "AI agent security", "MCP security", "tool calling safe", "RAG security", "OWASP LLM", "system prompt leak", "AI API key leaked", "unexpected OpenAI bill", "unexpected Anthropic bill", "agent permissions", "can the agent be tricked", "AI inference provider attack" or "is it safe to give the agent shell access"; when a project calls an LLM API, defines tools or agents, runs an MCP server, or loads third-party skills or plugins; and as a pass in any audit of an AI feature. Defensive security only. By Devleck.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.