Anthropic-Cybersecurity-Skills: 818 Structured Agent Skills Across Six MITRE and NIST Frameworks
817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io standard · Works with Claude Code, GitHub Copilot, Codex CLI, Cursor, Gemini CLI & 20+ platforms · 29 security domains · Apache 2.0
At a glance
- What is it?
- This community repository packages 818 cybersecurity skills for AI agents, each tagged to relevant MITRE ATT&CK, NIST CSF, ATLAS, D3FEND, AI RMF, and F3 framework IDs. It is a structured knowledge layer for agentic security tools, but its real value depends on how well your agent can use the mappings.
- Who is it for?
- Adopt this library if you run AI agents for security analysis and need a ready-made, framework-tagged skill set that can accelerate incident response, threat hunting, or fraud detection tasks. Skip it if you expect turnkey automation or if your workflows rely on proprietary, uncategorized skill formats.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 16 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What the library actually provides
The repository is a collection of 818 structured cybersecurity skills, each formatted to the agentskills.io open standard. The README describes these as giving an AI agent the knowledge of a senior analyst: which Volatility3 plugin to run on a memory dump, which Sigma rules catch Kerberoasting, and how to scope a cloud breach across providers. The skills span 34 security domains, from malware analysis to OSINT and cloud security. Each skill carries mappings to the frameworks that fit its subject. For example, a forensics skill might map to ATT&CK and NIST CSF, while an AI-security skill adds ATLAS and AI RMF. The library is not a tool or a script; it is a knowledge corpus that you point your agent at. The README stresses it is a community project, not affiliated with Anthropic, and includes offensive techniques that require explicit authorization to use.
Framework coverage and mapping logic
The mappings are not uniform across all skills. The README reports that 805 skills map to MITRE ATT&CK, 804 to NIST CSF 2.0, 139 to D3FEND, 97 to NIST AI RMF, 94 to MITRE F3, and 93 to ATLAS. That distribution makes sense: ATT&CK and CSF are near-universal for security work, while the other four frameworks apply only to specific skill types. The mapping is per-skill, not one-to-one. A skill like analyzing-network-traffic-of-malware carries ATT&CK technique T1071, CSF category DE.CM, ATLAS technique AML.T0047, D3FEND technique D3-NTA, and AI RMF function MEASURE-2.6. Another skill, detecting-business-email-compromise, maps to ATT&CK T1566, CSF DE.AE, and F3 technique F1005.006. This selective tagging is a deliberate design choice, and it means a user cannot assume every skill carries all six frameworks. The F3 coverage is notable because the framework was only released in April 2026, and the library already includes 94 fraud-relevant skills mapped to its tactics.
How the skills are meant to be used
The README says you clone the repository and point your agent at it. The skills follow the agentskills.io standard, which is designed to work with Claude Code, GitHub Copilot, Codex CLI, Cursor, Gemini CLI, and more than 20 other platforms. The exact mechanics of how an agent consumes these skills are not detailed in the README. There is no mention of a plugin, an MCP server, or a specific configuration file. The phrase 'point your agent at it' suggests the skills are files that the agent can read or load as context. The repository includes a playground link to Casky.ai and a mention of Hermes Agent compatibility, but those are external services. For a user, the practical step is to clone the repo, choose the skills relevant to a task, and provide them to the agent, likely as part of a prompt or a skill directory. The absence of a setup script or installation instructions is a gap; the README does not describe how to install or activate the skills beyond cloning.
Getting started: commands and configuration
The only explicit command in the README is to clone the repository: git clone of the repo URL. There is no install step, no package manager dependency, and no environment variable to set. The skills are presumably files in a directory structure, but the README does not show that structure. The materials mention a CONTRIBUTING.md and a SECURITY.md, which suggests the project expects users to read those files before contributing or using offensive skills. The license is Apache 2.0, which permits commercial use and modification, but you must retain the license notice. The README also points to a survey link and a playground waitlist, but those are promotional, not functional. For a hands-on start, a user would clone the repo, inspect the skill folders, and then feed a specific skill file to their agent as part of a task description. The lack of a quick-start guide beyond cloning is a limitation for non-experts.
Limitations and wrong-tool cases
The library is a knowledge base, not an execution engine. It does not run commands, parse logs, or enforce safety. The README warns that it includes dual-use techniques like red-team C2 and phishing simulation, and that you are solely responsible for lawful use. That means it is the wrong tool if you want a fully automated security assistant that can take actions without human review. The skills are text descriptions; they do not include code that executes. Another limitation is the dependency on the agentskills.io standard. If your agent platform does not support that standard, you will have to write a converter. The README claims compatibility with 26+ platforms, but it does not explain how that compatibility works. The coverage numbers also show that only 139 skills map to D3FEND and 93 to ATLAS, so if your work is heavily focused on defensive countermeasures or AI-specific threats, you will find fewer relevant skills. Finally, the project is community-maintained, with no corporate backing, so the long-term maintenance is uncertain.
A real alternative: raw framework data
Instead of using a pre-built skill library, you could directly access the MITRE ATT&CK and NIST CSF data via their official repositories or APIs. ATT&CK provides STIX/JSON bundles that describe techniques, tactics, and procedures. NIST CSF 2.0 is available as a spreadsheet or JSON. The difference in approach is that raw framework data gives you authoritative, up-to-date definitions, but it does not include the analyst-level guidance that this library adds, like which Volatility3 plugin to run or which Sigma rule to use. You would have to build that contextual knowledge yourself. The Anthropic-Cybersecurity-Skills library adds a layer of practical, skill-oriented instructions on top of the framework IDs. If you need strict compliance with the latest framework versions, raw data is safer because you control the update cycle. If you need operational know-how, this library saves you the effort of writing it from scratch.
Maintenance and license considerations
The repository shows active development: release v1.3.0 on 2026-06-22, v1.2.0 on 2026-04-06, and v1.1.0 on 2026-03-21. The last push is dated 2026-08-31, which is recent relative to the material. The release notes for v1.2.0 mention 'Five Framework Coverage', and v1.1.0 mentions 753 skills, so the library grew from 753 to 818 over three months. That pace suggests a responsive maintainer, but it also means the skill content can change quickly, which could break any custom tooling you build around it. The Apache 2.0 license is permissive, but the README includes an explicit warning about authorized use, which is a usage restriction that goes beyond the license. The project also has a CONTRIBUTING.md, so you can submit improvements, but you must follow the community guidelines. Before adopting it, check the SECURITY.md to understand the project's own security policy, and verify that the framework versions cited (ATT&CK v19.1, CSF 2.0, ATLAS 2026.07, D3FEND v1.4.0, AI RMF 1.0, F3 v1.1) match the versions you need for compliance reporting.
Editorial conclusion
Adopt this library if you run AI agents for security analysis and need a ready-made, framework-tagged skill set that can accelerate incident response, threat hunting, or fraud detection tasks. Skip it if you expect turnkey automation or if your workflows rely on proprietary, uncategorized skill formats. Before integrating, verify the skill content quality by sampling a few skills in your target domain, confirm the agentskills.io standard is supported by your agent platform, and check the license and contribution guidelines for any use restrictions.
Community notes