dag-permission-validator

Validate DAG agent child permissions against parent permission matrices.

10|1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/curiositech/windags-skills --skill dag-permission-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dag-permission-validator
Source: https://github.com/curiositech/windags-skills/tree/main/skills/dag-permission-validator
Command: npx skills add https://github.com/curiositech/windags-skills --skill dag-permission-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates permission inheritance between parent and child agents to ensure child permissions are equal to or more restrictive than the parent. This prevents privilege escalation across DAG-spawned agents and enforces consistency with organization policies.

Core Features & Use Cases

  • Pre-spawn validation to prevent unsafe permission requests and policy violations.
  • Violation reporting with actionable guidance and integration with dag-scope-enforcer and related components.
  • Policy-aware enforcement across core tools, file systems, networks, and MCP tools.

Quick Start

Provide a parent permission matrix and a proposed child matrix to receive validation results.

Frequently Asked Questions about dag-permission-validator

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

FAQPage Schema
What is permission inheritance validation for DAG agents?

Permission inheritance validation ensures child agents spawned in a DAG have permissions equal to or more restrictive than the parent. It prevents privilege escalation by validating the permission matrix before agent spawning occurs.

How do I prevent privilege escalation when spawning child agents in a DAG?

To prevent privilege escalation across DAG-spawned agents, apply pre-spawn validation using a permission matrix model. This enforces that child permissions across core tools, bash, file systems, networks, and MCP tools remain equal to or more restrictive than the parent.

Do I need a permission matrix to validate agent spawning policies?

Yes, you need a parent permission matrix and a proposed child matrix. The validator compares these matrices across core tools, bash, file system, network, MCP tools, and models to ensure child permissions do not exceed parent permissions.

What's the best way to enforce consistent security policies across DAG agents?

The best way to enforce policy consistency is pre-spawn validation against a permission matrix. This approach checks child agent permissions before spawning, reports violations, and provides actionable suggestions to align with organization security policies.

What happens when a child agent requests more permissions than the parent?

When a child agent requests more permissions than the parent, the validator generates a violation report. This report includes actionable guidance and warnings indicating which specific tools or resources exceed the allowed permission inheritance boundaries.