| Framework Home | Cross-Pillar Governance | AISM | NEXUS | Dashboard |
The canonical skill moved (2026-10). It now lives at
ai-safe2-secure-build-copilot/SKILL.md.skills/is no longer a skill package. A skill is the whole folder around itsSKILL.md, and this folder also holds the MCP server’s code and its prompt-injection test corpus, so installingskills/as a skill would hand that corpus to the model. The skill trust gate correctly rejected it.
Use the Technology Contribution Profile and Technology Card for tool/skill reviews. Distinguish inspecting an artifact from enforcing an action and testing its effects. The validation guide covers poisoned skills, forged process evidence, and probabilistic authorization. Skill trust verdicts and screening scores are not organizational AISM levels or assurance ratings.
The MCP server implementation and executable helpers use the applicable code license, currently MIT unless explicitly designated otherwise. Framework methodology, taxonomy content, and framework-based SKILL.md guidance retain the CC BY-SA 4.0 documentation designation. Preserve notices for third-party skills and dependencies. See Licensing by component.
The skills/ surface packages AI SAFE² guidance for AI assistants and provides the Python MCP server used for live control lookup and governance workflows.
The current v3.1 data model separates the stable core taxonomy from the protocol profile overlay:
skills/mcp/data/ai-safe2-controls-v3.0.json 161-control core taxonomy
skills/mcp/data/mcp-profile-v3.1.json CP.5.MCP profile, MCP-1 through MCP-19
The v3.0 filename on the core taxonomy is intentional historical provenance. AI SAFE² v3.1 did not add new core controls; it updated the MCP profile and enforcement model.
skills/
├── README.md
├── ai-safe2-secure-build-copilot/ Canonical framework skill (installable package)
│ ├── SKILL.md
│ └── SKILL-CARD.md
├── skill-spec.md Model-neutral behavior specification
├── evals.md Regression/evaluation expectations
├── chatgpt/gpt-instructions.md ChatGPT-facing instructions
├── gemini/gem-instructions.md Gemini-facing instructions
├── perplexity/system-instructions.md
└── mcp/
├── README.md MCP server setup and architecture
├── src/mcp_server/ Server implementation
├── data/
│ ├── ai-safe2-controls-v3.0.json
│ └── mcp-profile-v3.1.json
└── tests/
Use ai-safe2-secure-build-copilot/SKILL.md as the primary framework context and follow the target product’s supported method for project or system instructions.
Use the AI SAFE² MCP Server. It exposes core-control lookup plus the separate v3.1 MCP profile.
Use chatgpt/gpt-instructions.md and provide the core taxonomy/profile artifacts required for the use case.
Use gemini/gem-instructions.md together with the relevant framework data artifacts.
| Capability | Purpose |
|---|---|
lookup_control |
Search the 161 core controls and v3.1 MCP profile controls by ID or text |
risk_score |
Apply the AI SAFE² combined risk model |
compliance_map |
Reuse control evidence across mapped frameworks |
code_review |
Review implementation patterns against applicable controls |
agent_classify |
Estimate ACT tier and surface governance requirements |
| governance resources | Retrieve policy, schema, and workflow guidance |
See skills/mcp/README.md for current transport, authentication, compatibility, and MCP-19 limitations.
| Item | v3.1 state |
|---|---|
| Core framework controls | 161 |
| Core Cross-Pillar controls | CP.1 through CP.10 |
| MCP profile controls | MCP-1 through MCP-19 |
| Current MCP binding | 2026-07-28 |
| Legacy MCP binding | 2025-11-25, migration compatibility |
| Canonical skill | skills/ai-safe2-secure-build-copilot/SKILL.md |
| NEXUS role | CSI reference implementation, not mandatory dependency |
UAS is a 27-requirement regulatory profile extension, not CP.11, and does not add new controls to the 161-control core.
Skills and MCP tools help users interpret and operationalize AI SAFE². They do not create conformance merely by being installed.
A conformant implementation must satisfy the applicable control outcomes and produce the required evidence. For MCP, this includes the v3.1 profile requirements relevant to the deployment, including authorization/resource binding when MCP-19 applies.
| Framework Home | Cross-Pillar Governance | AISM | NEXUS | MCP Server | Scanner | Dashboard |
AI SAFE² v3.1 · Cyber Strategy Institute