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-dashboardgit 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-dashboard)<a href="https://agentmods.dev/commands/ashlrai/ashlr-plugin/ashlr-dashboard"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-plugin/ashlr-dashboard.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.00034 | $0.00477 |
| Opus 5 | $0.00017 | $0.00238 |
| Sonnet 5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
ashlr-dashboard 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 5d 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.
What it actually says
Run the dashboard script via Bash and show the user its output verbatim.
Steps:
-
Run this command:
bun run ${CLAUDE_PLUGIN_ROOT}/scripts/savings-dashboard.tsIf
$CLAUDE_PLUGIN_ROOTis unset, fall back to resolving the plugin root by walking up from the current command file to find.claude-plugin/plugin.json, or use the path already known from other ashlr commands. -
Print the script's stdout verbatim inside a fenced code block (```) so the ANSI colors, Unicode box-drawing, bar charts, and sparklines all render correctly. The script is self-contained — it reads
~/.ashlr/stats.jsondirectly and renders a multi-panel view. -
Do not paraphrase, re-order, or summarize the numbers. The dashboard is the output — the user wants to see it as-is.
-
After the verbatim block, add at most one short line of context:
- If the dashboard shows the "No stats.json found yet" panel: "Run any
ashlr__read,ashlr__grep, orashlr__editcall and this dashboard will come alive." - If the projection section says "Not enough history yet": "Check back after a few more days of activity — the projection unlocks with ≥3 active days in the last 30."
- Otherwise: say nothing extra. The dashboard speaks for itself.
- If the dashboard shows the "No stats.json found yet" panel: "Run any
Pricing note (only surface if asked): the dashboard uses a blended $5/M-token rate derived from Claude Sonnet 4.5 pricing ($3/M input, $15/M output) as a rough honest estimate for read-heavy workloads.
If $ARGUMENTS contains --by-tool, also run:
bun run "${CLAUDE_PLUGIN_ROOT}/scripts/session-log-report.ts"
Append its stdout verbatim under a ## By tool section after the main dashboard block. Display it inside a fenced code block so column alignment renders correctly.
Related: /ashlr-savings gives the compact text-only version.
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.
- 5d ago First seen · 38 lines · 34 tokens per session scan A 88b3bfc7bf21
ashlr-dashboard is a command published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed 5d ago), licensed MIT. It adds 34 tokens to every session and 477 once invoked, about $0.0002 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
upgrade-webkit
Upgrade Bun's WebKit fork to the latest upstream version of WebKit.
dedupe
Find duplicate GitHub issues.
rp-build-cli
Build with rp-cli context builder → chat → implement.
specsync-create-spec
Create a new spec-sync module spec.
scriptwriter-draw
Draw a random chaos card from the 13-card deck — a plot-twist prompt the user can use as a scene seed, a basistext for an RRR cascade, or a riff for a room contribution.
nimbus-embedding-routing
Hybrid 384/1536-dim embedding routing (Phase 5 T6 PR 3): PROSEHEAVYTYPES, EMBEDDINGDIMLOCAL/EMBEDDINGDIMOPENAI, the RoutingEmbeddingPipeline wrapper, dual-table search (vecitems384 + vecitems1536 via vectorSearchChunksDual), the V30 migration (1536-dim table + dim-aware delete triggers), the nimbus index reembed CLI +…