mapping-pod-to-cloud-credential-reach SKILL.md skillA
mapping-pod-to-cloud-credential-reach from unboundcompute/security-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add unboundcompute/security-agent-skills/mapping-pod-to-cloud-credential-reach@git:20260828.ce55026Pins git:20260828.ce55026 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- unboundcompute/security-agent-skills
- Path
skills/mapping-pod-to-cloud-credential-reach/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260828.ce55026, committed Aug 28, 2026
- Size
- 9,008 bytes
- Repository stars
- 26
- License
- MIT
Map what cloud identity a compromised pod can reach and what that identity can then do: a pod bound to a workload identity or role far broader than it needs, a node instance role reachable from any pod through the node metadata endpoint, a service-account token mounted into a pod that federates to cloud, and the chain from one pod's credential to another cloud resource or identity. Covers Kubernetes on cloud where pods obtain cloud credentials through workload identity federation, mounted…
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
# Mapping pod-to-cloud credential reach: the blast radius of one compromised pod A pod on a cloud-hosted cluster is rarely just a container; it is a holder of cloud credentials. It may bind to a workload identity, mount a service-account token that federates to a cloud role, or simply sit on a node whose instance role is reachable through the node metadata endpoint. So the real question about a pod is not what it does but what its credentials reach: if this pod is compromised, which cloud APIs, data stores, and other identities does its token open, and can it chain from there to something larger. The dangerous pattern is a modest workload holding a broad credential, or any pod able to reach the node role, because the blast radius is the credential, not the application. You map this by identifying every credential a pod holds or can reach and enumerating what each can do. ## When to use - Pods obtain cloud credentials through workload identity federation, mounted tokens, or the node role. - The node metadata endpoint may be reachable from pods, exposing the node instance role. …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/mapping-pod-to-cloud-credential-reach@sha256:cc9e624593ed0312The line at the top of this page pins the label git:20260828.ce55026, 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_3u3yvs7ivzzn3dho)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 28, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9008 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 link to a raw IP address
- pass: No script tag
Source
unboundcompute/security-agent-skills · 26 stars · license MIT · pushed 2026-09-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3u3yvs7ivzzn3dho GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/mapping-pod-to-cloud-credential-reach GET https://markdownregistry.com/api/v1/blob/cc9e624593ed03129432fc35f8722cfc8c0dc08eecd448830c7bf2f5294dc8d5
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.