Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/ancoleman/ai-design-components/architecting-securitynpx skills add ancoleman/ai-design-components --skill architecting-securitygit clone --depth 1 https://github.com/ancoleman/ai-design-componentsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ancoleman/ai-design-components/architecting-security)<a href="https://agentmods.dev/skills/ancoleman/ai-design-components/architecting-security"><img src="https://agentmods.dev/badge/skills/ancoleman/ai-design-components/architecting-security.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00062 | $0.05517 |
| Opus 5 | $0.00031 | $0.02759 |
| Sonnet 5 | $0.00012 | $0.01103 |
| Haiku 4.5 | $0.00006 | $0.00552 |
Grade A, and why
architecting-security scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Architecture
Design and implement comprehensive security architectures that protect systems, data, and users through layered defense strategies, zero trust principles, and risk-based security controls.
Purpose
Security architecture provides the strategic foundation for building resilient, compliant, and trustworthy systems. This skill guides the design of defense-in-depth layers, zero trust implementations, threat modeling methodologies, and mapping to control frameworks (NIST CSF, CIS Controls, ISO 27001).
Unlike tactical security skills (configuring firewalls, implementing authentication, scanning vulnerabilities), security architecture focuses on strategic planning, comprehensive defense strategies, and governance frameworks.
When to Use This Skill
Use security architecture when:
- Designing security for greenfield systems (new applications, cloud migrations)
- Conducting security audits or risk assessments of existing systems
- Implementing zero trust architecture across enterprise environments
- Establishing security governance programs and compliance frameworks
- Threat modeling applications, APIs, or microservices architectures
- Selecting and mapping security controls to regulatory requirements (SOC 2, HIPAA, PCI DSS)
- Designing cloud security architectures (AWS, GCP, Azure multi-account strategies)
- Addressing supply chain security (SLSA framework, SBOM implementation)
Core Security Architecture Principles
1. Defense in Depth
Implement multiple independent layers of security controls so that if one layer fails, others continue to protect critical assets.
9 Defense Layers (2025 Model):
- Physical Security: Data center access, environmental controls, hardware security modules (HSMs)
- Network Perimeter: Next-gen firewalls (NGFW), DDoS protection, web application firewalls (WAF)
- Network Segmentation: VLANs, VPCs, security groups, micro-segmentation
- Endpoint Protection: EDR, antivirus, device encryption, patch management
- Application Layer: Secure coding, WAF, API security, SAST/DAST scanning
- Data Layer: Encryption (at-rest, in-transit, in-use), DLP, backup/recovery
- Identity & Access Management: MFA, SSO, RBAC/ABAC, privileged access management (PAM)
- Behavioral Analytics: UEBA, ML-based anomaly detection, threat intelligence
- Security Operations: SIEM, SOAR, incident response, continuous monitoring
What ships with it
21 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/architectures/aws-multi-account-security.md 26 KB
- examples/architectures/azure-landing-zone.md 34 KB
- examples/architectures/gcp-security-hierarchy.md 31 KB
- examples/architectures/zero-trust-network.md 36 KB
- examples/threat-models/api-threat-model.md 26 KB
- examples/threat-models/microservices-threat-model.md 43 KB
- examples/threat-models/web-app-stride.md 15 KB
- outputs.yaml 12 KB
- references/aws-security-architecture.md 4.0 KB
- references/azure-security-architecture.md 2.2 KB
- references/cis-controls.md 4.6 KB
- references/defense-in-depth.md 23 KB
- references/gcp-security-architecture.md 1.9 KB
- references/iam-patterns.md 2.0 KB
- references/nist-csf-mapping.md 13 KB
- references/owasp-top10-mitigation.md 6.4 KB
- references/security-operations.md 1.3 KB
- references/supply-chain-security.md 15 KB
- references/threat-modeling.md 21 KB
- references/zero-trust-architecture.md 23 KB
- scripts/security-checklist.sh 6.3 KB runs code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 501 lines · 62 tokens per session scan A 314b9f2f3833
architecting-security is a skill published in the GitHub repository ancoleman/ai-design-components (518 stars, last pushed 8mo ago), licensed MIT. It adds 62 tokens to every session and 5,517 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
Brand
Complete brand development system with emotive foundation. Triggers on requests for brand identity, logos, visual systems, or design guidelines. Creates distinctive, anti-AI-slop design from strategy through delivery.
canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Art
AI image generation tool. Use when you need to generate reference images, illustrations, or visual content from text prompts.
superdesign
Design or redesign frontend UI, presentations, and graphics on the Superdesign canvas with a choice of leading AI models. Use whenever the user wants to design a page, feature, flow, slide deck, or brand-new product; improve or reproduce existing UI; compare design results across top models; explore visual variants…
paint
Paint a complete visual universe with genjutsu - art direction brainstorm, design system, implementation, audit. Anti-AI-slop design pipeline. Adapts to Web, Android (Compose), Apple (SwiftUI).