agent-architecture-audit
Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature.
npx skills add mturac/everything-openai-codex --skill agent-architecture-audit --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Agent Architecture Audit A diagnostic workflow for agent systems that hide failures behind wrapper layers, stale memory, retry loops, or transport/rendering mutations. ## When to Activate **MANDATORY for:** - Releasing any agent or LLM-powered application to production - Shipping features with tool calling, memory, or multi-step workflows - Agent behavior degrades after adding wrapper layers - User reports "the agent is getting worse" or "tools are flaky" - Same model works in playground but breaks inside your wrapper - Debugging agent behavior for more than 15 minutes without finding root cause **Especially critical when:** - You've added new prompt layers, tool definitions, or memory systems - Different agents in your system behave inconsistently - The model was fine yesterday but is hallucinating today - You suspect hidden repair/retry loops silently mutating responses **Do not use for:** - General code debugging — use `agent-introspection-debugging` - Code review — use language-specific reviewer agents - Security scanning — use `security-review` or `security-review/scan` - Agent performance benchmarking — use `agent-eval` - Writing new features — use the appropriate workflow
- When to Activate
- The 12-Layer Stack
- Common Failure Patterns
- 1. Wrapper Regression
- 2. Memory Contamination
- 3. Tool Discipline Failure
- 4. Rendering/Transport Corruption
- 5. Hidden Agent Layers
- Audit Workflow
- Phase 1: Scope
- Phase 2: Evidence Collection
- Phase 3: Failure Mapping
- Phase 4: Fix Strategy
- Severity Model
Tool requirements expressed only in prompt text (not code) rg "must.*tool|必须.*工具|required.*call" --type md Tool execution without validation rg "tool_call|toolCall|tool_use" --type py --type ts Hidden LLM calls outside main agent loop rg "completion|chat\.create|messages\.create|llm\.invoke" Memory admission without user-correction priority rg "memory.*admit|long.*term.*update|persist.*memory" --type py --type ts Fallback loops that run additional LLM calls rg "fallback|retry.*llm|repair.*prompt|re-?prompt" --type py --type ts
What does the agent-architecture-audit skill do?
Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature.
How do I install it?
Run `npx skills add mturac/everything-openai-codex --skill agent-architecture-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mturac/everything-openai-codex, a repository with 84 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
