dag-permission-validator

Validate child agent permissions against parent security boundaries.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/rauly-1408/order-saas --skill dag-permission-validator-rauly-1408
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dag-permission-validator
Source: https://github.com/rauly-1408/order-saas/tree/main/.claude/skills/dag-permission-validator
Command: npx skills add https://github.com/rauly-1408/order-saas --skill dag-permission-validator-rauly-1408

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents security violations in agent workflows by validating that child agent permissions never exceed the permissions granted to parent agents.

Core Features & Use Cases

  • Permission Inheritance Validation: Compares parent and child permission matrices to detect unauthorized escalation across tools, files, networks, and models.
  • Security Policy Checking: Validates permission boundaries before agent spawning and identifies specific violations with corrective suggestions.
  • Use Case: Ensure a multi-agent development workflow safely creates child agents with restricted access while maintaining strict organizational security policies.

Quick Start

Use the dag-permission-validator skill to check whether a child agent permission matrix is safely inherited from its parent agent configuration.

Frequently Asked Questions about dag-permission-validator

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

FAQPage Schema
How do I validate agent permission inheritance in multi-agent orchestration?

Agent permission inheritance validation compares parent and child permission matrices to prevent child agents from exceeding security boundaries. It checks tool access, filesystem rules, network restrictions, and execution permissions to enforce restrictive child configurations.

What is permission inheritance validation for agent workflows?

Permission inheritance validation is a security mechanism that ensures child agents never exceed the permissions granted to their parent agents. It detects unauthorized escalation across tools, files, networks, and models in multi-agent workflows.

Can I check security boundaries before spawning a child agent?

Yes, you can perform pre-spawn checks to validate permission boundaries before agent spawning. This process identifies specific security violations and provides corrective suggestions to ensure child configurations remain restrictive.

How do I prevent child agents from exceeding parent security boundaries?

To prevent child agents from exceeding parent security boundaries, validate permission inheritance by comparing tool access, filesystem rules, network restrictions, and execution permissions to enforce restrictive child configurations.

What's the best way to review a permission matrix for multi-agent workflows?

The best way to review a permission matrix for multi-agent workflows is to validate agent permission inheritance, which compares parent and child configurations to detect unauthorized escalation across tools, files, networks, and models.

Why does a child agent need permission validation in a DAG workflow?

A child agent needs permission validation in a DAG workflow to maintain strict organizational security policies. Validation ensures child agents have restricted access and never exceed the security boundaries granted to their parent agents.