Menu
Write and read agex tracking events.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Install or uninstall backend-native hooks that track usage via agex hook write.
Show available lessons, or teach one.
Render a descriptive markdown snapshot of the project's current agent setup.
Install usage tracking hooks and build a levelup skill to advise the user.
Read agex usage tracking data and suggest a next-feature-to-learn for the user.
Audit the current project's agent setup and suggest 1-2 next improvements.
| name | hook |
| description | Write and read agex tracking events. |
| type | command |
agex hook write <event> [key=value ...] / agex hook read --agent <backend>writeCalled by installed hooks (see agex gamify, Phase 7). Appends a JSON line to .agex/data/<event>.json. Silent. Safe for concurrent invocation (file locking via portalocker).
agex hook write post-tool-use tool=Read
readRenders tracked events as a markdown table. Prints the source JSON path for deeper inspection.
agex hook read --agent claude-code
post-tool-use, user-prompt, stop, sessions.key=value pairs are captured into the payload. Empty keys (e.g., =foo) are dropped.ts) is attached automatically; a positional ts=<value> overrides it (useful for replays).<event> name is authoritative — it always wins over any event=... pair in args..agex/data/*.json (e.g., from a partial write) are skipped with a warning on hook read, not raised.