- Installs
- 41
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/gmh5225/awesome-ai-security --skill awesome-ai-security-overview- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads awesome-ai-security-overview automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Awesome AI Security - Project Overview
Purpose
This is a curated collection of AI/ML security materials and resources for pentesters, red teamers, and security researchers. The goal is to keep the list AI-focused, high-signal, well-categorized, and non-duplicated.
Project Structure
awesome-ai-security/
├── README.md # Main resource list (curated)
├── LICENSE # License
├── .claude/
│ └── skills/ # Claude skills (this directory)
└── ref/ # Reference notes (not curated)
├── my_collect.md # Personal collection
├── Awesome-AI-Security-1/
├── awesome-ai-security-2/
├── 模型安全/ # Model security notes
├── 渗透测试相关/ # Pentesting notes
└── 网络安全相关/ # Network security notes
README.md Format Convention
Heading Structure
- Top-level categories use
##. - Subcategories use
###(e.g., insideAI Security & Attacks). - Starter Pack uses bold bullets for sub-sections (e.g.,
- **CTFs / Practice**).
Link Format
- Use full URLs, one per bullet line.
- Add a short description in square brackets:
- https://... [Short description] - Keep descriptions concise.
- Do not add the same URL in multiple places.
Example Entry
### Prompt Injection
- https://github.com/example/tool [Prompt injection detector]
Categorization Rules (How to Place a New Link)
- AI Security Starter Pack: CTFs, courses, blogs, newsletters, beginner resources.
- AI/LLM Guide: LLM fundamentals, tutorials, awesome lists.
- AI Security & Attacks: Prompt injection, adversarial attacks, poisoning, privacy, model security.
- AI Pentesting & Red Teaming: AI-powered pentesting tools, red teaming, MCP security tools.
- AI Security Tools & Frameworks: AI vulnerability detection, CVE analysis, OSINT, security libraries, TLS / fingerprint / bot signals (JA3 clients, site bot detection, automation hardening research—use only ethically and on authorized targets).
- AI Agents & Frameworks: Agent frameworks, formal methods / Lean agents (e.g. AI-assisted theorem proving orchestration), AI memory & long context (latent memory, recursive context, long-memory RAG), RAG stacks/collections, browser automation, MCP servers, agent sandboxes & isolation (policy-enforced runtimes, container/VM boundaries).
- AI Development & Training: Training frameworks, local models, uncensored models, prompts.
- AI Applications: Chat assistants, deep research, search engines, code analysis, web scraping, vision / domain apps (e.g. agricultural or specialized image understanding with LLMs).
- AI Image & Video: Image generation, video generation, TTS, face recognition.
- Benchmarks & Standards: AI safety benchmarks, threat frameworks, standards.
AI-Relevance Filter
Only include AI/ML-related resources. Do not add:
- Traditional security tools (unless AI-powered)
- Web3/blockchain tools (unless AI-related)
- General pentesting tools without AI integration
- Browser vulnerabilities, phishing tools, CVE collections (unless AI-analyzed)
Duplicate Policy
No duplicate URLs in README.md. If a link fits multiple categories, pick the primary one.
Contribution Checklist
- Check for duplicates in
README.mdbefore adding. - Verify the resource is AI/ML-related.
- Verify the link points to the canonical source (avoid low-value forks).
- Keep the description concise and useful.
- Put it into the most appropriate category.
- Prefer minimal changes over reformatting large sections.
Utilities Section
End of README.md includes Utilities (mixed): agent-facing CLIs, productivity, and mail/identity (e.g. self-hosted domain mail, encrypted P2P email) when they support ops or privacy around AI workflows—keep entries concise.
Data Source
For detailed and up-to-date resources, fetch the complete list from:
https://raw.githubusercontent.com/gmh5225/awesome-ai-security/refs/heads/main/README.md
Use this URL to get the latest curated links when you need specific tools, papers, or resources.
FAQ
What does the awesome-ai-security-overview skill do?
Guide for understanding and contributing to the awesome-ai-security curated resource list. Use this skill when adding resources, organizing categories, or maintaining README.md consistency (no duplicates).
How do I install awesome-ai-security-overview?
Run npx skills add https://github.com/gmh5225/awesome-ai-security --skill awesome-ai-security-overview in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/awesome-ai-security-overview/ (personal) or .claude/skills/awesome-ai-security-overview/ (project).
Which AI agents can use awesome-ai-security-overview?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is awesome-ai-security-overview safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains awesome-ai-security-overview?
It is published by gmh5225 in gmh5225/awesome-ai-security. It has 41 recorded installs.
More from gmh5225/awesome-ai-security
ai-powered-pentesting
gmh5225/awesome-ai-security
Open the skill to read its SKILL.md instructions.
llm-attacks-security
gmh5225/awesome-ai-security
Open the skill to read its SKILL.md instructions.
adversarial-machine-learning
gmh5225/awesome-ai-security
Open the skill to read its SKILL.md instructions.
ai-security-tooling
gmh5225/awesome-ai-security
Guide for AI security tooling (detectors, analyzers, guardrails, benchmarks) and consistent placement in README.md.
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.