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 agentmods add commands/rupakm/leslie/ox-session-stopgit clone --depth 1 https://github.com/rupakm/leslieWrote 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/commands/rupakm/leslie/ox-session-stop)<a href="https://agentmods.dev/commands/rupakm/leslie/ox-session-stop"><img src="https://agentmods.dev/badge/commands/rupakm/leslie/ox-session-stop.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00388 |
| Opus 5 | $0.00000 | $0.00194 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade C, and why
ox-session-stop scanned grade C with 1 finding 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 2d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Keep this file thin. Behavioral guidance (use-when, common-issues, errors) belongs in the ox CLI JSON output (guidance field), not here. Skills are agent-specific wrappers; ox serves all agents (Codex, etc.). Except What it actually says
Stop recording and save this agent session to the project ledger.
Post-Command
After the command completes, check the JSON output for guidance and summary_prompt fields.
Follow the guidance field for next steps.
If summary_prompt is present (sync mode):
- Read the prompt carefully — it references the raw session file on disk
- Read the raw session file at the path specified in the prompt
- Generate the summary JSON following the Output Format in the prompt
- Save it to a temporary file (e.g.,
.ox-summary.jsonin the workspace root, or/tmp/ox-summary.json) — do NOT write to the session cache dir as it may be outside the workspace sandbox - If the prompt includes a
push-summarystep, run that command with--filepointing to your temp file - Verify the push succeeded by checking the JSON output for
"success": true - Clean up the temporary summary file
If summary_prompt is absent (async mode):
No agent action required. Upload and summary generation happen automatically in the background.
If summary generation fails:
- Run
ox agent <id> doctor— it can detect and help recover missing summaries - The session data is safe regardless; only the rich summary is missing
$ox agent session stop
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.
- 2d ago First seen · 31 lines · 0 tokens per session scan C eae57b042174
ox-session-stop is a command published in the GitHub repository rupakm/leslie (14 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 388 tokens. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.