Auto skill build agent run ledger dashboard

Skill Arnie016/codex-prompt-templates/skills/auto-skill-build-agent-run-ledger-dashboard

Color-coded Codex prompt templates and Agent Skills for plugin-orchestrated AI coding workflows, MCP safety, repo intelligence, and automation.

Install

npx -y skills add Arnie016/codex-prompt-templates --skill auto-skill-build-agent-run-ledger-dashboard

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Append and summarize a lightweight local `.agent-runs/runs.jsonl` ledger (claudetop-inspired) so Codex sessions build durable observability over time. Use at the end of a significant task, after running tests, or when you want a quick “what did we do lately?” dashboard. Skip when the user only wants a one-off fix and does not care about tracking runs.

SKILL.md

1.9 KB, as published. Nobody here has run it

Agent Run Ledger Dashboard

Generated by: Codex Supercharge maintenance automation.

Goal: cheap, append-only run tracking without relying on proprietary telemetry.

Append a run entry

Run from the repo you worked in:

python3 plugins/codex-supercharge/scripts/agent_runs_append.py \
  --task "Fix flaky auth tests" \
  --model "${CODEX_MODEL:-}" \
  --status ok \
  --command "pytest -q" \
  --notes "Root cause: clock mocking"

Notes:

--model defaults to $CODEX_MODEL when set.
The script records current git branch/head + uncommitted diff stats when available.

View a dashboard summary

python3 plugins/codex-supercharge/scripts/agent_runs_report.py --days 7 --last 20

Recommended workflow

After completing a task, run the append command once.
When starting work, run the report command to see recent context.
If you want richer fields (tokens/cost), add them as new keys; keep JSONL append-only.

Skip when

The repo is sensitive and you cannot persist local logs.
The task is a trivial one-liner and you are not doing longitudinal tracking.

References

plugins/codex-supercharge/references/agent-run-ledger.md
Pattern inspiration only (do not run blindly): sources/claudetop

Validation

Appending creates exactly one JSONL record for the run.
Reports summarize the requested window without rewriting the ledger.
Sensitive task notes are summarized or omitted before persistence.