auditing-message-broker-topic-authorization SKILL.md skillA
auditing-message-broker-topic-authorization 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-message-broker-topic-authorization@git:20260829.b60f9b2Pins git:20260829.b60f9b2 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-message-broker-topic-authorization/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260829.b60f9b2, committed Aug 29, 2026
- Size
- 9,822 bytes
- Repository stars
- 26
- License
- MIT
Audit message-broker topic and queue authorization for reach a client should not have: a wildcard subscription that receives another tenant's messages, a publish permission broad enough to inject into a control or command topic, a shared broker where topic naming is the only separation between tenants, and a client authenticated to the broker but not authorized per topic so any connection can read or write any topic. Covers MQTT, Kafka, AMQP, and similar brokers where publish and subscribe…
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 message-broker topic authorization: when a wildcard subscribes to everyone A message broker is a shared channel that many producers and consumers, often many tenants, talk through, and topic authorization is what keeps one client's messages from reaching another's. That boundary is thinner than it looks. Authenticating to the broker is not the same as being authorized per topic: a broker that checks the connection but not the topic lets any authenticated client read or write any topic. Wildcards make it worse, a subscription with a wildcard can match another tenant's topics and receive their messages, and a broad publish permission can inject into a control or command topic that consumers act on. And on a shared broker, topic naming is frequently the only thing separating tenants, which is a convention, not an enforced boundary. The audit asks, for each client, exactly which topics it can publish to and subscribe to, and whether that matches its role. You audit this by enumerating effective topic permissions and testing cross-tenant reach. ## When to use - A broker (MQTT, Kafka, AMQP, or similar) carries messages across producer, consumer, or tenant boundaries. …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/auditing-message-broker-topic-authorization@sha256:d42bb55172a8cf8fThe line at the top of this page pins the label git:20260829.b60f9b2, 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_wpszbh3lfwdqtnfw)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 29, 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 (9822 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_wpszbh3lfwdqtnfw GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/auditing-message-broker-topic-authorization GET https://markdownregistry.com/api/v1/blob/d42bb55172a8cf8f3383ca80a9960275dd6345c4912db33ac917052c39808346
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.