auditing-subagents

Auditing subagents involves validating YAML frontmatter and XML structure while evaluating role definitions, workflows, constraints, and tool usage. This produces severity-based, actionable findings with contextual judgment to ensure robust, compliant configurations.

A subagent configuration review checks YAML frontmatter, XML structure, role definitions, workflow specifications, constraints, and tool usage. It evaluates these elements against best practices to produce severity-based, actionable audit findings.

You validate YAML frontmatter and XML structure by running an audit on the subagent configuration file path. The audit enforces checks against best practices to identify structural issues and deliver actionable findings.

Yes, you can evaluate subagent workflows, constraints, and tool usage for larger orchestration tasks. The audit reviews the configuration to ensure safe, reliable, and effective orchestration by providing severity-based findings.

The best way to get severity-based findings is to audit the subagent configuration file path against best practices. This evaluates the XML structure, workflows, and constraints to deliver actionable results with contextual judgment.

No specific dependencies are required to review subagent YAML and XML configurations. You provide the subagent configuration file path to audit, and it evaluates the frontmatter and structure against best-practices references.