agentwhy-session-audit

Checks which private files (.env, keys, secrets) Claude Code and its subagents reached in this project, whether a value came into an agent's context, and which key to change, by running the open source agentwhy CLI over the session records Claude Code already keeps on disk. Use when the user asks whether the agent or a subagent read their .env or other secrets, which private files a session touched, whether a key leaked into the conversation, or which key to rotate. Runs locally and never prints

Install

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• ask-matt 323,485 ★
  Ask which skill or flow fits your situation. A router over the skills in this repo.
• chief-of-staff 323,485 ★
  Pursue a long-running goal in a single session by co-ordinating subagents.
• claude-handoff 323,485 ★
  Hand the current conversation off to a fresh background agent that picks up the work immediately.
• grill-me 323,485 ★
  A relentless interview to sharpen a plan or design.
• grilling 323,485 ★
  Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thin