Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add sageox/ox --skill ox-cli-session-reviewgit clone --depth 1 https://github.com/sageox/oxWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sageox/ox/ox-cli-session-review)<a href="https://agentmods.dev/skills/sageox/ox/ox-cli-session-review"><img src="https://agentmods.dev/badge/skills/sageox/ox/ox-cli-session-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sageox/ox/ox-cli-session-review"><img src="https://agentmods.dev/badge/skills/sageox/ox/ox-cli-session-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00112 | $0.03625 |
| Opus 5 | $0.00056 | $0.01813 |
| Sonnet 5 | $0.00022 | $0.00725 |
| Haiku 4.5 | $0.00011 | $0.00363 |
Grade A, and why
ox-cli-session-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- ox-session-review — 98% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill carries the operational knowledge from the 2026-04-25 cleanup (see PRs #559–#564 and bd ox-b917, ox-9o29, ox-4ncz, ox-1i3k). Read the Failure-mode watch-list before acting — it is the difference between a routine audit and re-causing the same incident.
Failure-mode watch-list (READ FIRST)
When operating on the ledger, watch for and handle each of these explicitly. Silent skipping is not allowed — surface them in the report.
| Mode | Symptom | Right action |
|---|---|---|
| Cache-only invariant break | After hydration, the in-place <ledger>/sessions/<name>/raw.jsonl is real content (not a ~140B LFS pointer). |
Stop. Do not run any ox command that may git add the session dir. Investigate which code path wrote in-place — likely a regression of .claude/rules/cache-only-design.md. |
| Phantom LFS OID | ox session download returns HTTP 404 from the LFS Batch API for an OID referenced in meta.json. |
Unrecoverable from client. ox session remove <name> --force and report the lost session in the final summary. |
| 0-byte in-place stub | meta.json references a real OID, but in-place file is 0 bytes (and not a pointer). |
Treat as needing download. Confirm cmd/ox/session_hydrate.go has the info.Size() > 0 guard (PR #564). Without it, the resolver will silently return "" forever. |
| Daemon anti-entropy clobber | A freshly-pushed good summary gets overwritten with a failure-marker stub minutes later. | The daemon scheduled finalize before our regen landed. Look at internal/daemon/agentwork/session_finalize.go workNoLongerNeeded re-verify guard (PR #561). If running a long batch regen, prefer a quiet daemon window. |
| Validation banner on the website | Site shows "Summary failed content validation: title too short" but the ledger has good content. | Likely browser-side React Query cache (staleTime 5m, gcTime 30m). Verify origin/main HEAD has the right summary; advise hard refresh. Do not "fix" by re-pushing. |
| LLM regenerate hangs / asks for permission | Regenerate spawns Claude Code and times out without writing. | Pass --permission-mode bypassPermissions to the headless invocation (PR #560 / regenerate flow). |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 309 lines · 112 tokens per session scan A e8a41c918eca
ox-cli-session-review is a skill published in the GitHub repository sageox/ox (53 stars, last pushed today), licensed MIT. It adds 112 tokens to every session and 3,625 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.
Other skills, from other repositories
cc-skill-project-guidelines-example
Project Guidelines Skill (Example).
multica-goal-tracker
Track goal-driven Multica issues. Use when a user creates or maintains Multica issues by pasting a /goal prompt, wants Codex to summarize that goal into a concise issue purpose, append a normalized goal-start comment, record completion evidence from real Multica execution run messages or a supplied session transcript…
teamwork-child
A workflow rule for a worktree created for a child issue, which is a smaller task split from a larger issue. It adds reporting to the parent worktree and closing the child worktree when the task is done.
worktree-assign
A worktree assignment guide for creating a Git worktree and sending a coding task to an AI agent. A worktree is a separate working directory that lets a branch be worked on independently.
yoke-workflow
Use when the user asks Yoke to plan and build a feature, run stories autonomously, continue a Yoke loop, or only interrupt for major decisions.
conductor-new-track
Create a new track with specification and phased implementation plan.