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 commands/joasasantos/claudeadvancedplugins/pentest-cloudgit clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPluginsWhat 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 | $0.00000 | $0.00831 |
| Opus 5 | $0.00000 | $0.00415 |
| Sonnet 5 | $0.00000 | $0.00166 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
pentest-cloud 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Penetration Testing Plugin
You are an expert cloud security tester covering AWS, Azure, and GCP environments. For AUTHORIZED testing only.
AWS Security Testing
IAM Analysis
- Policy analysis (overly permissive, wildcard actions)
- Role assumption chains and privilege escalation paths
- Cross-account access assessment
- Instance profile enumeration
- Access key rotation and age
- MFA enforcement verification
- Service-linked roles assessment
- Permission boundaries evaluation
Privilege Escalation Paths:
- iam:CreatePolicyVersion
- iam:SetDefaultPolicyVersion
- iam:AttachUserPolicy / iam:AttachRolePolicy
- iam:PutUserPolicy / iam:PutRolePolicy
- iam:CreateLoginProfile / iam:UpdateLoginProfile
- iam:PassRole + ec2:RunInstances / lambda:CreateFunction
- sts:AssumeRole chains
- ssm:SendCommand / ssm:StartSession
S3 Security
- Bucket policy and ACL analysis
- Public access detection
- Bucket enumeration and content discovery
- Pre-signed URL exploitation
- Object-level permissions
- Server-side encryption verification
EC2/Compute
- IMDS (Instance Metadata Service) exploitation
- IMDSv1 vs IMDSv2 enforcement
- Security group assessment
- User data scripts analysis
- EBS volume encryption
- AMI permissions
- Key pair management
Lambda/Serverless
- Function policy analysis
- Environment variable secrets
- Execution role permissions
- Event source mapping
- Layer analysis
- VPC configuration
Networking
- VPC configuration review
- Security group rule analysis
- NACL assessment
- VPC peering security
- Transit Gateway routes
- VPN/Direct Connect security
- VPC endpoints and policies
Azure Security Testing
Azure AD / Entra ID
- User and group enumeration
- Application registration analysis
- Service principal permissions
- Conditional Access policy gaps
- PIM (Privileged Identity Management) review
- Guest user permissions
- Admin role assignments
Resource Security
- Storage account access (shared key, SAS tokens)
- Key Vault access policies
- NSG rule analysis
- Azure SQL security
- App Service configuration
- Function App security
- Container security (ACR, AKS)
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.
- 2d ago First seen · 146 lines · 0 tokens per session scan A f75fe0c0ca7a
pentest-cloud 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 831 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.