audit-agent-guidance

Audits durable agent guidance files against intended behavior, evidence, and client semantics.

Updated May 12, 2026
One-click install
npx skills add https://github.com/mtk177a/skills --skill audit-agent-guidance-mtk177a
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-agent-guidance
Source: https://github.com/mtk177a/skills/tree/main/skills/audit-agent-guidance
Command: npx skills add https://github.com/mtk177a/skills --skill audit-agent-guidance-mtk177a

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent instructions like AGENTS.md, CLAUDE.md, and SKILL.md often fail to produce the intended behavior, but it is hard to tell whether the cause is wording, loading order, precedence, trigger conflicts, or missing evidence. This Skill diagnoses guidance systems against intended behavior and observed usage before any revision is made. ## Core Features & Use Cases - Behavior-first diagnosis: States the expected behavior and failure signals before inspecting artifacts, separating symptoms from root causes. - Cross-surface auditing: Examines instruction files, Skills, references, policy files, and client configuration together, including authority, precedence, triggers, and context cost. - Third-party trust analysis: Traces provenance, scripts, data access, and outbound destinations of imported Skills as one combined capability chain. - Use Case: When agents ignore a policy written in AGENTS.md, use this Skill to determine whether the file actually loaded, which instruction won precedence, and whether the fix should be a local edit or a structural reorganization. ## Quick Start Audit my AGENTS.md and SKILL.md files as one guidance system and explain why the agent is not following the retry policy, with evidence and a validation plan.

Frequently Asked Questions about audit-agent-guidance

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

FAQPage Schema
How do I audit why agents ignore my AGENTS.md instructions?▼

Define the intended behavior and failure signals first, then gather loading traces, precedence rules, and usage evidence before inspecting the file wording. The audit separates symptoms from root causes and labels behavior unconfirmed when no behavioral evidence exists.

What is the difference between auditing guidance and designing new agent instructions?▼

Auditing diagnoses existing durable guidance against intended behavior and evidence, while designing creates new instruction sets or Skills. Use design-skill or design-agent-instructions for new authoring, and this audit only for diagnosing what already exists.

Can this audit review third-party Skills for security risks?▼

Yes, it traces provenance, remote instructions, scripts, filesystem access, and outbound destinations as one combined capability chain rather than isolated permissions. It does not perform standalone line-by-line vulnerability reviews of script implementations.

Does the audit modify my guidance files automatically?▼

No, the audit is read-only by default and only reports findings, alternatives, and a validation plan. Edits happen only when the user explicitly authorizes changes and the environment policy permits them.

When should I not use an agent guidance audit?▼

Do not use it for ordinary pull request diff review, standalone Codex .rules command-policy review, or designing brand-new Skills. Those tasks belong to review-changes, a dedicated policy review, or design-skill respectively.