cloud-iam-deep SKILL.md skillF
cloud-iam-deep from elementalsouls/claude-bughunter is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add elementalsouls/claude-bughunter/cloud-iam-deep@git:20260605.5de6a68Pins git:20260605.5de6a68 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- F, 15 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- elementalsouls/claude-bughunter
- Path
skills/cloud-iam-deep/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260605.5de6a68, committed Jun 5, 2026
- First version recorded
- May 15, 2026
- Size
- 25,564 bytes
- Repository stars
- 7,555
- License
- MIT
Cloud IAM red-team attack chain across AWS, Azure, GCP — focused on EXTERNAL exploitation paths and post-credential-discovery privilege analysis. Covers IAM enumeration (aws iam, az role, gcloud iam), STS/AssumeRole chaining, Azure Managed Identity abuse (via SSRF/leak), GCP service account JSON abuse, IMDSv1/v2 attacks via SSRF, K8s ServiceAccount token privilege analysis once held (token discovery / cluster exposure is owned by hunt-k8s), role-trust-policy confused-deputy, cross-account…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## When to use
Trigger when:
- A cloud credential surfaces (key, secret, token, JSON file)
- SSRF chain reaches IMDS / metadata endpoint
- APK / git-leak reveals embedded cloud key
- Recon shows public S3/GCS/Azure-blob with permissions you can verify
- A Kubernetes API or service-account token is exposed
- Post-RCE on a cloud-hosted instance — pivot to cloud control plane
Do NOT use for:
- On-prem-only environments (use AD attack skills — but those are out of scope per external-only boundary)
- Web2 vulns that happen to be on AWS — use the relevant `hunt-*` skill
---
## Credential identification (first 60 seconds)
```bash
# AWS access key patterns
AKIA[0-9A-Z]{16} # IAM user access key (long-term)
ASIA[0-9A-Z]{16} # STS temporary credential
AGPA[0-9A-Z]{16} # IAM group
AIDA[0-9A-Z]{16} # IAM user (user-id)
AROA[0-9A-Z]{16} # IAM role
ANPA[0-9A-Z]{16} # Managed policy
# AWS secret pattern (40-char base64-ish — context required)
[A-Za-z0-9/+=]{40} # AWS secret access key
# Azure
AccountKey=[A-Za-z0-9+/=]{86} # Storage account key
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_yizgvf5htrjlm26s/d495d06f40392ac410fadd40e35b0a3acbe921aba99a0a9946ed5b26abc64ea9.json
Then /plugin install cloud-iam-deep@markdownregistry-yizgvf5htrjlm26s in Claude Code. It installs git:20260605.5de6a68, the one graded F here, pinned to the commit it was graded at, and leaves it there.
mdr add elementalsouls/claude-bughunter/cloud-iam-deep@sha256:d495d06f40392ac4The line at the top of this page pins the label git:20260605.5de6a68, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_yizgvf5htrjlm26s)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in elementalsouls/claude-bughunter/cloud-iam-deep since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of cloud-iam-deep from somewhere else? Ask it: where did my cloud-iam-deep come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between May 15, 2026 and Jun 5, 2026, about one every 7 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260605.5de6a68 latest | 2026-06-05 | 5de6a68 | 25,564 B | F | view · diff |
| git:20260525.c42e50d | 2026-05-25 | c42e50d | 25,483 B | F | view · diff |
| git:20260515.5f39300 | 2026-05-15 | 5f39300 | 18,202 B | F | view · diff |
| git:20260515.cc78522 | 2026-05-15 | cc78522 | 16,839 B | F | view |
Copies
1 file in 1 other repository holds the exact bytes of one of this file's versions, each committed after this file had them: it holds an older version.
- adriannoes/awesome-agentic-ai · cursor-claude-codex/skills/bug-hunter/skills/cloud-iam-deep/SKILL.md · 2 versions behind · 100 stars
A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/cloud-iam-deep/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- FAIL, critical: No credential-shaped string (matched: -----BEGIN PRIVATE KEY-----)
- fail: No link to a raw IP address (matched: http://169.254.169.254)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (25564 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
elementalsouls/claude-bughunter · 7,555 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yizgvf5htrjlm26s GET https://markdownregistry.com/api/v1/resolve?ref=elementalsouls/claude-bughunter/cloud-iam-deep GET https://markdownregistry.com/api/v1/blob/d495d06f40392ac410fadd40e35b0a3acbe921aba99a0a9946ed5b26abc64ea9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from elementalsouls/claude-bughunter
Every file in elementalsouls/claude-bughunter