cloud-config SKILL.md skillB
cloud-config from dragonked2/alphacode is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dragonked2/alphacode/cloud-config@git:20260929.29bbcb8Pins git:20260929.29bbcb8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dragonked2/alphacode
- Path
src/alphacode_base/bundled_skills/bugbounty/cloud-config/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260929.29bbcb8, committed Sep 29, 2026
- Size
- 7,012 bytes
- Repository stars
- 626
- License
- MIT
Cloud and platform configuration assessment — object storage public access, over-permissive IAM, instance metadata reachability, exposed Kubernetes and container registry APIs, managed identity trust, and secret material in the open. Read-only assessment methods; see IMPACT BOUNDARY.
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
# CLOUD AND PLATFORM CONFIGURATION
**Core:** most cloud findings are **read-only reachability tests**. You prove a
misconfiguration exists from outside. You do not use the access it grants.
The line between "assessing a cloud misconfiguration" and "using stolen cloud
credentials" is the entire legal and ethical boundary of this skill, and it is
not a grey area.
---
## PART 1 — WHAT IS IN SCOPE
A cloud misconfiguration is only in scope if the **cloud account is named in the
scope file**, or the program states that cloud infrastructure is in scope.
Many bug bounty programs scope only the web application and explicitly exclude
third-party SaaS and cloud accounts.
```
READ the program policy for:
- "cloud infrastructure" / "hosted services" in scope?
- explicit exclusions: "no testing of our cloud account",
"AWS/GCP/Azure out of scope", "no credential testing"
- safe-harbor wording that covers configuration review
```
**If the cloud account is not named, stop.** An S3 bucket found via a
subdomain is still the company's asset, but the authorization comes from the
program policy, not from the fact that you found it. Check before you probe.
---
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_pzyyxts6n3ealusk/d88f5b32651044262586162734eb8a09dec03f3ad17e85dd8f8497571402df15.json
Then /plugin install cloud-config@markdownregistry-pzyyxts6n3ealusk in Claude Code. It installs git:20260929.29bbcb8, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add dragonked2/alphacode/cloud-config@sha256:d88f5b3265104426The line at the top of this page pins the label git:20260929.29bbcb8, 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_pzyyxts6n3ealusk)
5 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 dragonked2/alphacode/cloud-config 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-config from somewhere else? Ask it: where did my cloud-config 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 1 version of this file, committed on Sep 29, 2026.
Watch this file (sign in, one email per new version)
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-config/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: 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 (7012 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 credential-shaped string
- 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
dragonked2/alphacode · 626 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pzyyxts6n3ealusk GET https://markdownregistry.com/api/v1/resolve?ref=dragonked2/alphacode/cloud-config GET https://markdownregistry.com/api/v1/blob/d88f5b32651044262586162734eb8a09dec03f3ad17e85dd8f8497571402df15
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.