auditing-namespace-as-tenant-boundary SKILL.md skillA
auditing-namespace-as-tenant-boundary 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-namespace-as-tenant-boundary@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-namespace-as-tenant-boundary/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260828.ce55026, committed Aug 28, 2026
- Size
- 9,470 bytes
- Repository stars
- 26
- License
- MIT
Audit a Kubernetes namespace that is treated as a tenant isolation boundary for the isolation it does not actually provide: cluster-scoped resources and nodes shared across namespaces, RBAC that grants a tenant reach beyond its own namespace, missing network policy so pods cross namespaces freely, and shared cluster services (DNS, ingress, admission, storage classes) that see or serve every tenant. Covers multi-tenant clusters where each tenant is given a namespace and the namespace is assumed…
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 the namespace as a tenant boundary: what a namespace does not isolate A namespace is a name-scoping and policy-attachment unit, not a security sandbox, yet multi-tenant clusters routinely hand each tenant a namespace and assume it contains them. It does not, on its own. Nodes are shared, so a tenant that can influence scheduling or escape a container reaches another tenant's pods on the same node. Cluster-scoped resources, custom resource definitions, node objects, persistent volumes, and cluster roles sit outside every namespace and are visible or reachable across them. RBAC that grants a verb at cluster scope, or on another namespace, punches straight through the boundary. Without network policy, pods cross namespaces freely. And the shared cluster services every tenant depends on, DNS, ingress, admission, storage classes, see or serve all tenants at once. The audit question is not whether tenants have separate namespaces but whether the namespace actually stops one from affecting or observing another. You audit this by testing each isolation the boundary is assumed to provide. ## When to use …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/auditing-namespace-as-tenant-boundary@sha256:400ff8066af6e284The 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_uhrwxqwpilesqess)
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 (9470 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_uhrwxqwpilesqess GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/auditing-namespace-as-tenant-boundary GET https://markdownregistry.com/api/v1/blob/400ff8066af6e2841936263fbfed0e599f0d5420fe6dff405c51b940c100b436
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.