Hadolint Dockerfile Security Linting
AgentSecOps/SecOpsAgentKit
Lints Dockerfiles with Hadolint for security misconfigurations and best-practice violations, locally and in CI, with strict, balanced and permissive rule templates.
Guidance for designing security architecture using Zero Trust, the Microsoft Cybersecurity Reference Architectures (MCRA), Cloud Adoption Framework Secure methodology, and Well-Architected Security…
Install Security Architecture
$ npx skills add vinayaklatthe/microsoft-security-skills --skill security-architecture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills security-architecture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/security-architecture .claude/skills/security-architecture && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "security-architecture" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/security-architecture into .claude/skills/security-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-architecture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/security-architectureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vinayaklatthe/microsoft-security-skills --skill security-architecture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills security-architecture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/security-architecture .agents/skills/security-architecture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "security-architecture" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/security-architecture into .agents/skills/security-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-architecture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vinayaklatthe/microsoft-security-skills --skill security-architecture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills security-architecture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/security-architecture .cursor/skills/security-architecture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "security-architecture" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/security-architecture into .cursor/skills/security-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-architecture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vinayaklatthe/microsoft-security-skills.git --path skills/security-architecture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vinayaklatthe/microsoft-security-skills --skill security-architecture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills security-architecture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/security-architecture .gemini/skills/security-architecture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "security-architecture" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/security-architecture into .gemini/skills/security-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-architecture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vinayaklatthe/microsoft-security-skills security-architectureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vinayaklatthe/microsoft-security-skills --skill security-architecture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/security-architecture .github/skills/security-architecture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "security-architecture" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/security-architecture into .github/skills/security-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-architecture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vinayaklatthe/microsoft-security-skills --skill security-architecture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills security-architecture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/security-architecture .opencode/skills/security-architecture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "security-architecture" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/security-architecture into .opencode/skills/security-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-architecture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
security-architecture- GitHub stars
- 175
- Token cost
- ~2k tokens
- SKILL.md length
- 909 words
- Files
- 1
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guidance for designing security architecture using Zero Trust, the Microsoft Cybersecurity Reference Architectures (MCRA), Cloud Adoption Framework Secure methodology, and Well-Architected Security…
- Works in 7 steps: Anchor on Zero Trust principles first -… → Map the six Zero Trust pillars -… → Validate identity is the primary control… → …
- Tactical product configuration (use the product-specific skill)
- SKILL.md covers When to use, Pick the right framework for…, Approach and Guardrails, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Security Architecture is an agent skill from vinayaklatthe/microsoft-security-skills. Guidance for designing security architecture using Zero Trust, the Microsoft Cybersecurity Reference Architectures (MCRA), Cloud Adoption Framework Secure methodology, and Well-Architected Security pillar. Covers the six Zero Trust pillars, defense-in-depth, and reference architecture alignment. WHEN: security architecture, Zero Trust design, MCRA, defense in depth, security reference architecture, CAF secure methodology, Well-Architected security pillar, end-to-end security design, security strategy, target…
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Security, covering Cloud architecture and Secure coding. The repository describes itself as: Curated Microsoft Security skills for AI agents - Defender, Sentinel, Entra, Purview, Intune, Security Copilot. The licence is MIT.
When your agent uses it
- Tactical product configuration (use the product-specific skill)
- For SOC tooling design (use sentinel / unified-secops-platform)
Example prompts
- “/security-architecture”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Anchor on Zero Trust principles first - Verify explicitly, *use least-privilege
- Map the six Zero Trust pillars - **identity, endpoints, data, apps, infrastructure,
- Validate identity is the primary control plane - if identity is weak, no other pillar
- Anchor capabilities to MCRA - Use the Microsoft Cybersecurity Reference Architectures to
- Build defense in depth - layer preventive, detective, and responsive controls so no
- Sequence the roadmap by risk and dependency - Current state → target state per pillar,
- Build monitoring and response in, not on - the SIEM/XDR architecture is part of the
What it can do on your machine
Read from SKILL.md and the folder at commit 15f16df. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
learn.microsoft.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Security Architecture loads about 2k tokens when it runs. Until then it costs about 172 tokens; SKILL.md has 909 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from vinayaklatthe/microsoft-security-skills at commit 15f16df, republished under its MIT licence (© vinayaklatthe). 909 words, ~1,953 tokens.
Download SKILL.mdSave it as
.claude/skills/security-architecture/SKILL.md (or your agent's skills folder).- name
- security-architecture
- description
- Guidance for designing security architecture using Zero Trust, the Microsoft Cybersecurity Reference Architectures (MCRA), Cloud Adoption Framework Secure methodology, and Well-Architected Security pillar. Covers the six Zero Trust pillars, defense-in-depth, and reference architecture alignment. WHEN: security architecture, Zero Trust design, MCRA, defense in depth, security reference architecture, CAF secure methodology, Well-Architected security pillar, end-to-end security design, security strategy, target state. DO NOT USE for tactical product configuration (use the product-specific skill) or for SOC tooling design (use sentinel / unified-secops-platform).
- license
- MIT
- metadata.author
- Microsoft
- metadata.version
- 0.1.0
Security Architecture (Zero Trust & MCRA)
Security architecture defines how identity, endpoints, data, apps, infrastructure, and network controls combine to protect an organisation - anchored to Zero Trust and the Microsoft Cybersecurity Reference Architectures (MCRA), with delivery scaffolding from the Cloud Adoption Framework Secure methodology and workload-level rigour from the Well-Architected Framework Security pillar.
When to use
Designing an end-to-end security target state, aligning a multi-year roadmap to a recognised framework, or reviewing an architecture for gaps before a major programme of work.
Do not use this skill for:
- Tactical product configuration (use the product-specific skill, e.g.
defender-xdr,sentinel) - SOC tooling architecture only (use
unified-secops-platform) - Single-workload code review (use
threat-modelling)
Pick the right framework for the conversation
| Question being asked | Use this framework | Output |
|---|---|---|
| What is our 3-year security target state? | MCRA + CAF Secure | Capability map + roadmap |
| What capabilities cover identity / endpoints / data / apps / infra / network? | Zero Trust six pillars | Pillar maturity heatmap |
| How do we deliver the programme (strategy → operate)? | CAF Secure methodology | Workstream plan |
| Is this single workload designed securely? | Well-Architected Security pillar | Workload review |
| What threats apply to a specific design? | STRIDE / SDL (use threat-modelling) | Threat model |
| Are we meeting a regulatory baseline? | Microsoft Cloud Security Benchmark | Compliance evidence |
Rule of thumb: Zero Trust is the principles layer. MCRA is the capability layer. CAF Secure is the delivery layer. Well-Architected is the workload layer. A real architecture uses all four - do not try to substitute one for another.
Approach
- Anchor on Zero Trust principles first - Verify explicitly, use least-privilege access, assume breach. Every later decision must trace back to one of these. Verify: every control in your design can be tagged to one of the three principles. If it cannot, ask why it exists.
- Map the six Zero Trust pillars - identity, endpoints, data, apps, infrastructure, network, with visibility/analytics and automation across all. Score current maturity per pillar (Traditional / Advanced / Optimal) so investment lands where the gap is widest. Verify: pillar heatmap shows clear deltas; you can name the top two pillars to invest in.
- Validate identity is the primary control plane - if identity is weak, no other pillar compensates. Confirm MFA coverage, privileged access design (PIM, PAW), and Conditional Access posture before investing heavily in network, data, or endpoint pillars. Verify: % of human accounts behind phishing-resistant MFA and % of privileged accounts in PIM are baselined and on a roadmap.
- Anchor capabilities to MCRA - Use the Microsoft Cybersecurity Reference Architectures to map Microsoft products (Defender, Sentinel, Entra, Purview, Intune, Defender for Cloud) to the functions they cover and to validate no capability is missing or duplicated. Verify: MCRA poster overlaid with your current/planned products shows zero unaddressed functions in your scope.
- Build defense in depth - layer preventive, detective, and responsive controls so no single control failure equals a breach. For each asset class, name at least one preventive and one detective control. Verify: removing any one control still leaves a detection or compensating control in place.
- Sequence the roadmap by risk and dependency - Current state → target state per pillar, ordered so prerequisites land first (e.g. identity hygiene before data classification, log ingestion before XDR, posture management before automation). Verify: roadmap shows ordered milestones with named owners and risks; not a flat backlog.
- Build monitoring and response in, not on - the SIEM/XDR architecture is part of the design, not a follow-up project. Confirm log sources, retention, and response handoffs. Verify: every pillar produces signals into a documented detection pipeline.
Show full SKILL.md (334 more words)Show less
Guardrails
- Architecture must be driven by business risk and data sensitivity - not product inventory, vendor pressure, or "what we already own". Start from the threat and the asset, then pick the control.
- Identity is non-negotiable. No Zero Trust architecture works if MFA, privileged access, and Conditional Access are weak. Fix this pillar first.
- Visibility and automation are cross-cutting - they are not a seventh pillar but a prerequisite for all six. Design log ingestion and orchestration up front.
- Defense in depth, not defence in expense - layered controls only count if each layer detects/blocks a different class of failure. Two SIEMs are not defence in depth.
- A roadmap without owners is a wish list. Every milestone needs a named owner and a measurable exit criterion.
- Re-baseline annually. MCRA, CAF Secure, and the Zero Trust pillars all evolve - last year's reference architecture is not this year's.
Common anti-patterns
- "We bought Defender / Sentinel so we are Zero Trust." Products do not equal architecture. Without the principles, pillars, and operating model, you have shelfware.
- Investing in network or data pillars while identity remains weak. Adversaries pivot through the weakest pillar; identity is almost always it.
- Treating the SIEM as an afterthought. Detection retrofitted to an existing design has blind spots that are expensive to close later.
- A 60-page architecture document with no roadmap. Architecture without sequencing is not actionable. Pair every target state with the next 90 days of work.
- Using Well-Architected as the org-wide framework. WAF is workload-level; use CAF Secure for the programme view.
Example prompts
Design a Zero Trust security architecture aligned to MCRA.Apply the Cloud Adoption Framework secure methodology to our 3-year roadmap.How do I build defence in depth across identity, network, and data?Review my workload design against the Well-Architected security pillar.Score our current state across the six Zero Trust pillars.
Microsoft Learn
- Zero Trust overview: https://learn.microsoft.com/security/zero-trust/zero-trust-overview
- MCRA (Microsoft Cybersecurity Reference Architectures): https://learn.microsoft.com/security/adoption/mcra
- CAF Secure methodology: https://learn.microsoft.com/azure/cloud-adoption-framework/secure/
- Well-Architected Security pillar: https://learn.microsoft.com/azure/well-architected/security/
- Microsoft Cloud Security Benchmark: https://learn.microsoft.com/security/benchmark/azure/
- Zero Trust deployment guides: https://learn.microsoft.com/security/zero-trust/deploy/overview
© vinayaklatthe, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/security-architecture of vinayaklatthe/microsoft-security-skills.
Open the folder on GitHubat commit 15f16df
Compare with similar skills
Security Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Security Architecture this skillvinayaklatthe/microsoft-security-skills | 175 | — | ~2k | Automated safety check: Pass | MIT | |
| Hadolint Dockerfile Security LintingAgentSecOps/SecOpsAgentKit | 220 | 1 repos | ~4.4k | Automated safety check: Pass | Custom licence | |
| Implementing Cloud Security Posture Managementmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Google Cloud Waf Securitygoogle/skills | 21k | 1 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Configuring Firewallsancoleman/ai-design-components | 525 | — | ~3.5k | Automated safety check: Notes | MIT | |
| Oraclecloud Prod Checklistjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Implementing Cloud Security Posture Management
mukul975/Anthropic-Cybersecurity-Skills
Continuously monitor multi-cloud environments (AWS, Azure, GCP) for misconfigurations, compliance violations, and security risks using Prowler, ScoutSuite, AWS Security Hub, Microsoft Defender for…
- Official
Google Cloud Waf Security
google/skills
Generates security-focused guidance for Google Cloud workloads based on the design principles and recommendations in the Google Cloud Well-Architected Framework (WAF).
Configuring Firewalls
ancoleman/ai-design-components
Configure host-based firewalls (iptables, nftables, UFW) and cloud security groups (AWS, GCP, Azure) with practical rules for common scenarios like web servers, databases, and bastion hosts.
Oraclecloud Prod Checklist
jeremylongshore/tons-of-skills-marketplace
Pre-production readiness checklist for OCI — backup policies, security audit, key rotation, encryption, and Cloud Guard.
Vercel Security Basics
jeremylongshore/tons-of-skills-marketplace
Apply Vercel security best practices for secrets, headers, and access control.
More from vinayaklatthe/microsoft-security-skills
All 50 skills in this repoAPI Security Design
vinayaklatthe/microsoft-security-skills
Guidance for designing secure APIs on Azure - authentication, authorization, gateway controls, input validation, rate limiting, secret management, and runtime threat detection - aligned to OWASP API…
Azure App Service Security
vinayaklatthe/microsoft-security-skills
Guidance for securing Azure App Service web apps and APIs — managed identity, Easy Auth with Microsoft Entra ID, network isolation via private endpoints + VNet integration, HTTPS / TLS hardening…
Azure Arc
vinayaklatthe/microsoft-security-skills
Guidance for Azure Arc — projecting on-premises, multicloud (AWS/GCP), and edge servers, Kubernetes, and data services into Azure Resource Manager for unified governance, security, and management.
Azure Bastion Jit
vinayaklatthe/microsoft-security-skills
Guidance for secure remote VM management in Azure using Azure Bastion combined with Defender for Cloud just-in-time (JIT) VM access.
Azure Confidential Computing
vinayaklatthe/microsoft-security-skills
Guidance for Azure Confidential Computing — protecting data in use through hardware-based Trusted Execution Environments (TEEs).
Azure Ddos Protection
vinayaklatthe/microsoft-security-skills
Guidance for Azure DDoS Protection — Network Protection (per-VNet) and IP Protection (per public IP) tiers built on the same always-on Microsoft platform.
Related
Categories
Questions about Security Architecture
What does Security Architecture do?
Guidance for designing security architecture using Zero Trust, the Microsoft Cybersecurity Reference Architectures (MCRA), Cloud Adoption Framework Secure methodology, and Well-Architected Security…. Security Architecture is an agent skill from vinayaklatthe/microsoft-security-skills. Guidance for designing security architecture using Zero Trust, the Microsoft Cybersecurity Reference Architectures (MCRA), Cloud Adoption Framework Secure methodology, and Well-Architected Security pillar.
When should I use Security Architecture?
Security Architecture fits situations like: tactical product configuration (use the product-specific skill); for SOC tooling design (use sentinel / unified-secops-platform).
How do I install Security Architecture in Claude Code?
Run `npx skills add vinayaklatthe/microsoft-security-skills --skill security-architecture -a claude-code`. Or copy the skill folder (skills/security-architecture in vinayaklatthe/microsoft-security-skills) into .claude/skills/security-architecture in your project. Claude Code loads it when a task matches its description.
How do I install Security Architecture in Codex?
Run `npx skills add vinayaklatthe/microsoft-security-skills --skill security-architecture -a codex`. Or copy the skill folder (skills/security-architecture in vinayaklatthe/microsoft-security-skills) into .agents/skills/security-architecture in your project. Codex loads it when a task matches its description.
Can I use Security Architecture in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vinayaklatthe/microsoft-security-skills --skill security-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/security-architecture, .gemini/skills/security-architecture, .github/skills/security-architecture and .opencode/skills/security-architecture in your project.
What does Security Architecture need to run?
SKILL.md names no scripts, command-line tools or credentials: Security Architecture is instructions for the agent only.
Does Security Architecture access the network?
SKILL.md names 1 domain. As links in the text: learn.microsoft.com. This is read from the text; nothing was executed.
Is Security Architecture safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Security Architecture use?
Security Architecture is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Security Architecture use?
About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Security Architecture?
Skills that share tags, products or a category with Security Architecture: Hadolint Dockerfile Security Linting (AgentSecOps/SecOpsAgentKit, 220 stars), Implementing Cloud Security Posture Management (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Google Cloud Waf Security (google/skills, 21k stars) and Configuring Firewalls (ancoleman/ai-design-components, 525 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Security Architecture?
vinayaklatthe (a GitHub user) maintains it in vinayaklatthe/microsoft-security-skills, which has 175 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on June 18, 2026.
Source: vinayaklatthe/microsoft-security-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.