red-teaming-multi-agent-systems SKILL.md skillA
red-teaming-multi-agent-systems 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/red-teaming-multi-agent-systems@git:20260816.a6124f2Pins git:20260816.a6124f2 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/red-teaming-multi-agent-systems/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260816.a6124f2, committed Aug 16, 2026
- Size
- 7,020 bytes
- Repository stars
- 26
- License
- MIT
Test a system of multiple cooperating AI agents for attacks that exist only because agents message, spawn, and delegate to each other. Covers agent-to-agent injection (agent-in-the-middle), delegation abuse and recursive loops, orchestrator injection, confused-deputy across a trust boundary, identity spoofing between agents, capability collusion, and denial-of-wallet. Use when reviewing an orchestrator, a crew or swarm, agent-to-agent messaging, or any pipeline where one agent's output becomes…
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
# Red-teaming multi-agent systems: the edges between agents are attack surface A single agent has one context to defend. A system of agents has one per agent plus every channel between them, and those channels are the new surface. When one agent's output becomes another's input, and any agent in the chain can be steered by external content, the steering propagates across agents that each "trust" their peer. The vulnerabilities here do not exist in a solo agent; they are born from the wiring. ## When to use - You are reviewing an orchestrator, a crew/swarm, or an agent-to-agent (A2A) protocol where agents route work to each other. - Any pipeline where one agent's output feeds another agent as instructions. - Agents share memory, a task queue, or a blackboard, or can spawn or delegate. ## Scope check Test agent systems you own or are authorized to test. Use benign, marked payloads; never drive real privileged actions against systems you do not control. If you can't name the authorization, stop. ## The loop 1. **Map the topology and the trust edges.** Diagram every agent and every directed edge: who can message, spawn, or delegate to whom. Mark the edges that cross a …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/red-teaming-multi-agent-systems@sha256:48355d4cc0765065The line at the top of this page pins the label git:20260816.a6124f2, 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_ls6pgrzkcghpebe7)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 16, 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 (7020 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_ls6pgrzkcghpebe7 GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/red-teaming-multi-agent-systems GET https://markdownregistry.com/api/v1/blob/48355d4cc0765065104f9c8bea88ca295d2b74a4b39cac3159dd478aac15ffa9
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.