Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ashlrai/ashlr-plugin/plugin install ashlrWrote 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/ashlrai/ashlr-plugin/ashlr-resume)<a href="https://agentmods.dev/commands/ashlrai/ashlr-plugin/ashlr-resume"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-plugin/ashlr-resume.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.1 | $0.00027 | $0.00624 |
| Opus 5 | $0.00014 | $0.00312 |
| Sonnet 5 | $0.00005 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
ashlr-resume 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Show a compact summary of the most recent ashlr session so you can pick up exactly where you left off.
Usage
/ashlr-resume
/ashlr-resume <branch-name>
- No argument — summarizes the single most recent session regardless of branch.
- With a branch name — finds the most recent session whose timestamp overlaps
commits on that branch (cross-references via
git log), then labels the output with that branch.
What it shows
Last session (yesterday, 2h ago — saved 4.3M tokens ≈$12.90):
Branch: feature/auth-flow
Work dir: myapp (12 reads, 4 edits)
__tests__ (5 reads, 3 edits)
Patterns: ashlr__grep ×7, Grep ×2
Bash: Bash ×18, ashlr__bash ×3
Calls: 42 tool invocations
Resume? Suggested next steps based on the trail:
- Re-open myapp (last edits in this session)
- Re-run: Bash (used ×18 last session)
- Continue on branch: feature/auth-flow
Behavior
- Reads
~/.ashlr/session-log.jsonl(active file) plus up to two rotated backups (.jsonl.1,.jsonl.2). Read-only — never modifies the log. - If the log is missing or empty, prints "No prior sessions found — you're starting fresh."
- Token savings figures come from
session_endevents written at session close. If nosession_endis present, tokens-saved shows as 0.
Limitations
The session log records tool names and working directories, not individual file paths or the content of grep patterns / bash commands. As a result:
- "Work dir" shows the repository directory rather than specific file paths.
- "Patterns" shows which grep tools were invoked (and how many times), not the actual search strings.
- "Bash" shows call counts for bash-family tools, not the specific commands run.
Individual argument capture is not part of the session-log schema (v1) by design — arguments may contain secrets. A future schema version may add opt-in argument hinting.
Implementation
bun run ${CLAUDE_PLUGIN_ROOT}/scripts/session-resume.ts [<branch>]
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.
- 6d ago First seen · 73 lines · 27 tokens per session scan A 56160c03de34
ashlr-resume is a command published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed 6d ago), licensed MIT. It adds 27 tokens to every session and 624 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
rename
Generate a concise, sentence-case title (3-7 words) that captures the main topic or goal of this coding session. The title should be clear enough that the user recognizes the session in a list. Use sentence case: capitalize only the first word and proper nouns.
follow-up
Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…
help
Explain Ralph Wiggum technique and available commands.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
gws-keep
List and read Google Keep notes.
dashboard
Open the subscribetome dashboard to view and manage API keys and subscriptions.