agent-containment-reviewer

Trace propagation paths and containment controls in multi-agent systems.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill agent-containment-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-containment-reviewer
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/agent-containment-reviewer
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill agent-containment-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill reviews multi-agent systems to find where bad outputs, failures, or drift can spread, and it checks whether the system can stop that spread before it becomes a fleet-wide incident.

Core Features & Use Cases

  • Cascade analysis: Traces how one agent’s garbage output, latency, retries, or fan-out can propagate through downstream agents and shared resources.
  • Drift and inventory review: Checks whether every running agent is registered with an owner, purpose, autonomy level, baseline behavior, and a tested kill path.
  • Containment controls: Verifies circuit breakers, bounded retries, backpressure, checkpoints, rollback points, and authority-severing kill switches.
  • Use case: Review an autonomous document pipeline or agent fleet after a bad release, model upgrade, or unexplained behavior change to determine containment gaps and required safeguards.

Quick Start

Review our autonomous agent system for cascade risks, drift detection gaps, inventory coverage, and kill-switch design, and return severity-ranked findings with concrete containment controls.

Frequently Asked Questions about agent-containment-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop agent failure from spreading across a multi-agent system?

Agent containment is the practice of isolating bad outputs, drift, or latency in multi-agent systems before they cascade. It works by tracing propagation paths through downstream agents and shared resources, then applying circuit breakers, backpressure, and kill switches to stop the spread.

How do I review my autonomous agent pipeline for cascade risks after a model upgrade?

Review your autonomous agent pipeline by tracing how garbage output, latency, and fan-out propagate through downstream agents. Verify drift detection, inventory governance with registered owners, tested kill paths, and checkpoint rollback points to identify containment gaps after a model upgrade.

What is blast-radius isolation in multi-agent systems and when do I need it?

Blast-radius isolation in multi-agent systems is confining a failure to a single agent rather than allowing propagation. You need it when managing agent fleets or autonomous pipelines where unexplained behavior changes, drift, or bad outputs could cascade through shared resources.

Can I use checkpoint rollback and kill switches for an unregistered autonomous agent?

Using checkpoint rollback and kill switches requires registered agents with bounded trust. You cannot effectively contain an unregistered agent; inventory governance mandates that every running agent has an owner, purpose, autonomy level, behavioral baseline, and a tested credential-revoking kill path.

What's the best way to design a kill switch for an agent fleet?

The best way to design a kill switch for an agent fleet is to test credential-revoking stops and authority-severing controls. It requires bounded trust between agents, established behavioral baselines, and composed cost and incident handoffs to ensure the switch halts operations safely.