auditing-workload-secret-exposure-surface SKILL.md skillA
auditing-workload-secret-exposure-surface 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/auditing-workload-secret-exposure-surface@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/auditing-workload-secret-exposure-surface/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260828.ce55026, committed Aug 28, 2026
- Size
- 9,512 bytes
- Repository stars
- 26
- License
- MIT
Audit how a workload holds its secrets for the exposure that outlives the secret's intent: a secret passed as an environment variable that any process, crash dump, or child inherits and that debug endpoints echo, a secret volume mounted where a sidecar or a shared process can read it, a secret written into logs or an error, and a Kubernetes secret readable by more service accounts than the one workload that needs it. Covers containerized workloads where secrets reach the process through…
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
# Auditing workload secret exposure surface: who else can read this secret A secret a workload needs is safe only if nothing beyond the intended consumer can read it, and containerized delivery quietly widens that set. An environment variable is inherited by every child process, echoed by many debug and introspection endpoints, and captured in crash dumps and process listings, so an env secret is readable by far more than the code that meant to use it. A mounted secret file is readable by every container in the pod that shares the mount, so a sidecar becomes a reader. A secret that lands in a log line or an error message is exposed to whoever reads logs, which is usually a much broader audience than whoever holds the secret. And the orchestrator's secret object is readable by every identity its access rules admit, often more service accounts than the one workload. The audit is not whether the secret exists but who else can see it. You audit this by tracing each secret from its store into the workload and enumerating every other reader. ## When to use - Workloads consume secrets through environment variables, mounted files, or the orchestrator's secret store. …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/auditing-workload-secret-exposure-surface@sha256:5daa5bd36508845aThe 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_qpeyedh6q4i7pqfr)
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 (9512 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_qpeyedh6q4i7pqfr GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/auditing-workload-secret-exposure-surface GET https://markdownregistry.com/api/v1/blob/5daa5bd36508845a08c64a9bbdbe4050e2e29fb3d7d220b4508958452566f0c1
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.