Agent Editor
Write or load a subagent definition, set every option with best-practice checks as you go, and export it for Claude Code or Codex.
Small interactive tools I've built to answer specific questions, mostly about what AI models cost and how coding agents spend their context.
Write or load a subagent definition, set every option with best-practice checks as you go, and export it for Claude Code or Codex.
See what every Claude Code and Codex hook event receives on stdin and can print on stdout, then check a payload of your own against it.
Write or load a SKILL.md, set every frontmatter option with best-practice checks as you go, and export it for Claude Code or Codex.
Paste or load a Claude Code workflow script to see its agents, fan-outs, and phases as a diagram, check it for mistakes, and export it as a Codex workflow.
Check a CLAUDE.md or AGENTS.md for rules written as requests that should be a permission rule, a hook, or a required check.
Compare how much code your parallel agents open each day with how much one person can review well, and see how many agents that keeps fully reviewed.
See how much faster a task finishes when you split it across subagents, and how much more it costs, as serial work and integration eat the speedup.
Drop in your Claude Code session transcripts and find the failures that keep coming back, ranked by sessions affected, and how many come from your environment rather than the model.
See whether compacting a big context or switching to a cheaper model pays for itself before your coding session ends.
Is the difference between two ways of working real, or just noise? The same five tasks, read two ways, show why it depends on how you measured.
Compare what the same token usage costs across AI models, or drop in a Claude Code or Codex session to price its real usage on every model.
How much of a Claude Code context window is already spoken for before you’ve said anything, across five common setups, and which of those claims you can actually move.