← ClaudeAtlas

agent-architecture-auditlisted

Audit LLM and agent applications for wrapper regressions, prompt or memory contamination, tool discipline failures, hidden repair loops, and output rendering corruption. Use before shipping agent features or when an agent works in a direct model call but fails inside the product.
shipshitdev/skills · ★ 26 · AI & Automation · score 73
Install: claude install-skill shipshitdev/skills
# Agent Architecture Audit Diagnose failures in agent systems by inspecting each layer that can change the model's behavior between the raw model call and the final user-visible output. ## Contract Inputs: - Agent or LLM application repository, failing run, trace, log, or symptom - Optional model/provider list, tool definitions, memory files, and UI output Outputs: - Severity-ranked findings with evidence references - Layer-by-layer failure diagnosis - Ordered fix plan that prefers code gates over prompt-only changes Creates/Modifies: - None in audit mode - Follow-up fixes only when explicitly requested External Side Effects: - None by default - External logs, observability tools, or production systems only when already authorized Confirmation Required: - Before changing prompts, memory, tool contracts, persistence, production config, or user data Delegates To: - `debug` for ordinary software defects - `evaluation` or `advanced-evaluation` for benchmark design - `security-audit` for prompt injection, secrets, auth, or privileged tool risk ## When to Use - An agent works in a model playground or direct API call but fails in the app. - A wrapper, orchestration layer, memory system, or tool router was added and quality regressed. - The model skips required tools, claims tool use that did not happen, or misreads tool output. - Old conversation facts, stale memories, or compressed summaries leak into new tasks. - Logs show a correct answer but the CLI, API, U