I kept running into Claude Code subagents and skills that performed poorly, and I had no good way to investigate why. Traditional software has had profilers and debuggers for decades. When a request is slow or a function blows up memory, you instrument the process and dig in. Agentic development doesn’t have that yet. With agents, poor performance usually comes down to context: too many irrelevant tokens, or missing the relevant ones. So I built agent-profiler to investigate: Which tool calls were called each turn and how they impacted the context window What subagent/skills were spawned and what context they were passed. Which steps get repeated every session that could be lifted into a skill, doc, or cached lookup It’s free , open-source , requires zero setup beyond Node, runs fully locally , and works with any agent harness that produces a local transcript (Claude Code transcripts work out of the box). Repo: https://github.com/DevonPeroutky/agent-profiler Super happy to take feedback, feature requests, or bug reports. submitted by /u/Ill_Rip_9038
Originally posted by u/Ill_Rip_9038 on r/ClaudeCode
You must log in or # to comment.