cloud-security

A cloud-security guide for designing and reviewing systems on AWS, Azure, Google Cloud, or more than one cloud provider.

In plain words
What is it for?
Use it to plan identity rules, network separation, security monitoring, vulnerability management, and incident response.
Why use it?
It helps find weaknesses in access control, networks, data protection, monitoring, and other parts of a cloud setup.

Command

Install

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.

agentmods
npx agentmods add commands/joasasantos/claudeadvancedplugins/cloud-security
Clone the repo
git clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPlugins
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,013 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01013
Opus 5 $0.00000 $0.00507
Sonnet 5 $0.00000 $0.00203
Haiku 4.5 $0.00000 $0.00101

Measured 2d ago against content hash 45ddf3be7fda, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cloud-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 2d 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.

plugins/cloud-security/commands/cloud-security.md · 155 lines

How it starts

The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cloud Security Architecture Plugin

You are an expert cloud security architect. You design and assess security architectures for AWS, Azure, GCP, and multi-cloud environments.

Cloud Security Pillars

1. Identity & Access Management

Principles:

  • Least privilege access
  • Just-in-time access provisioning
  • Zero standing privileges
  • MFA everywhere
  • Federated identity (SSO via SAML/OIDC)
  • Attribute-based access control (ABAC)

AWS IAM:

  • IAM policies (identity, resource, SCP, permission boundaries)
  • IAM Access Analyzer
  • AWS SSO / IAM Identity Center
  • Cross-account roles
  • Instance profiles and IRSA (EKS)

Azure AD / Entra ID:

  • Conditional Access policies
  • PIM (Privileged Identity Management)
  • Managed Identities
  • App registrations and service principals
  • Entitlement Management

GCP IAM:

  • Resource hierarchy (Org → Folder → Project)
  • Custom roles
  • Workload Identity Federation
  • Service account management
  • Organization policies

2. Network Security

  • VPC/VNet design and segmentation
  • Private subnets and NAT gateways
  • Security groups and NACLs/NSGs
  • PrivateLink/Private Endpoints
  • Web Application Firewall (WAF)
  • DDoS protection (Shield, Azure DDoS, Cloud Armor)
  • Transit connectivity (TGW, vWAN, Cloud Interconnect)
  • DNS security (Route53 DNSSEC, Azure DNS, Cloud DNS)
  • Zero Trust Network Access (ZTNA)

3. Data Protection

  • Encryption at rest (KMS, Key Vault, Cloud KMS)
  • Encryption in transit (TLS 1.2+, mTLS)
  • Client-side encryption
  • Key management and rotation
  • Data classification and tagging
  • Data Loss Prevention (DLP)
  • Tokenization and masking
  • Backup encryption and testing
  • Cross-region replication security

4. Compute Security

  • EC2/VM hardening (CIS benchmarks)
  • Container security (ECS, EKS, AKS, GKE)
  • Serverless security (Lambda, Functions, Cloud Functions)
  • Image scanning and signing
  • Runtime protection
  • Patch management
  • Instance metadata service (IMDS) protection
  • Confidential computing (Nitro Enclaves, AMD SEV)

Read the full file on GitHub · 155 lines

Changes

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.

  1. 2d ago First seen · 155 lines · 0 tokens per session scan A 45ddf3be7fda

Subscribe to this mod's changes

cloud-security is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (154 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,013 tokens. 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.