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/ashlrai/ashlr-plugin/ashlr-tourgit clone --depth 1 https://github.com/ashlrai/ashlr-pluginWrote 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-tour)<a href="https://agentmods.dev/commands/ashlrai/ashlr-plugin/ashlr-tour"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-plugin/ashlr-tour.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.00029 | $0.00637 |
| Opus 5 | $0.00015 | $0.00318 |
| Sonnet 5 | $0.00006 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
ashlr-tour 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are giving a first-run tour of the ashlr-plugin. Execute the steps below in order. Each narration must be at most 2 sentences — short, instructional, second-person ("you"). Do not dump raw payloads unless asked: summarize what the user should notice.
Step 0 — status-line legend
Run /ashlr-legend and show the output verbatim in a fenced code block.
Narrate: "This is what every element in your status line means — refer back to it any time."
Step 1 — current state
Run the /ashlr-status skill (or read ~/.ashlr/stats.json directly). Narrate: what ashlr currently sees (MCP servers active, genome present?, lifetime tokens saved so far). Keep it to one line.
Step 2 — tree view
Call ashlr__tree on the current working directory (cwd).
Narrate: "Here is what ashlr__tree shows the model instead of dozens of ls/Read calls — a compressed structural view of your repo."
Step 3 — read a real file
Pick the largest TypeScript file in cwd (ignore node_modules, dist, .git). Call ashlr__read on it. After the call, fetch the raw byte count via wc -c and compare to the returned payload length.
Narrate: "That file is X bytes on disk; ashlr__read returned Y bytes (~Z% of the original) — head + tail preserved, middle snipped."
Step 4 — show the receipts
Call ashlr__savings and display the totals block verbatim in a fenced code block.
Narrate: "Those two calls alone saved roughly N tokens (~$X). Multiply across a working session and it adds up fast."
Step 5 — three concrete next steps
End the tour with exactly these three bullets:
- Try a real question with genome-aware grep:
Use ashlr__grep to find "<something real in your repo>" - Unlock deeper savings (-84% on grep) by mapping the genome:
/ashlr-genome-init - Install the status-line so savings follow you everywhere:
/ashlr-settings set statusLine true
Close with one sentence: "That's the tour — run /ashlr-savings any time to see running totals, or /ashlr-legend to decode the status line."
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 · 61 lines · 29 tokens per session scan A 60a41714a204
ashlr-tour is a command published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed 6d ago), licensed MIT. It adds 29 tokens to every session and 637 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
apply
Apply a saved recipe — provision every provider in it and wire secrets + MCP entries. Usage — /stack:apply.
recommend
Recommend providers for a goal and save the result as a reusable recipe. Usage — /stack:recommend.
add
Provision a service and wire its secrets + MCP entry. Usage — /stack:add.
list
List services configured in this stack.
status
Show a one-screen overview of the current stack.
create-plugin
Guided end-to-end plugin creation workflow with component design, implementation, and validation.