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.
git 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-leaderboard)<a href="https://agentmods.dev/commands/ashlrai/ashlr-plugin/ashlr-leaderboard"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-plugin/ashlr-leaderboard.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.00067 | $0.00587 |
| Opus 5 | $0.00034 | $0.00293 |
| Sonnet 5 | $0.00013 | $0.00117 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
ashlr-leaderboard 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 8d 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
Toggle participation in the public savings leaderboard shown at
https://plugin.ashlr.ai/community. Opt-in is OFF by default — nothing about
you is published until you explicitly run /ashlr-leaderboard on.
Usage
/ashlr-leaderboard on # opt IN — your GitHub handle + savings appear publicly
/ashlr-leaderboard off # opt OUT — removed from the public board on next sync
/ashlr-leaderboard status # show your current setting
What gets published when you opt in
- Your GitHub handle (e.g.
octocat) and avatar. - Your lifetime tokens saved and the dollar equivalent (at the published
$3/MTok rate — the same number
/ashlr-savingsshows you).
Never published: your email, your code, your prompts, file paths, or any per-session detail. Only the aggregate handle + savings figure.
How to apply this
The setting lives in ~/.ashlr/config.json under the leaderboard key:
on→ set{ "leaderboard": "public" }off→ set{ "leaderboard": "off" }status→ read the key and report:public(opted in),off(opted out), or unset (default — opted out).
Read the existing ~/.ashlr/config.json (create it as {} if missing), merge the
leaderboard key without disturbing other keys (e.g. telemetry), and write it
back. Then tell the user the change takes effect on the next stats sync
(session end), and confirm what is/isn't published.
Requirements & notes
- The leaderboard ranks developers whose stats sync to the cloud, which means a
signed-in account (Pro/Team — see
/ashlr-tier). Free users with only local stats won't appear even when opted in, because their savings never leave their machine. Mention this if the user isn't signed in. - Opting out removes you from the board after the next sync propagates the flag.
- This is the same privacy posture as
/ashlr-briefand telemetry: explicit, reversible, and off until you choose otherwise.
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.
- 8d ago First seen · 51 lines · 67 tokens per session scan A 8dfe16efd79f
ashlr-leaderboard is a command published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 587 once invoked, about $0.0003 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
familiar
Interact with your companion — show or change personality, mood, stats, and lore.
recall-save
Generate / overwrite .recall/context.md with Recall's local offline summarizer.
ccc-orchestrate
Sequential and tmux/worktree orchestration guidance for multi-agent workflows.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
complete
Signal that a skill's work is complete. Triggers downstream subscriptions with "when": "complete" timing. Automatically invoked — do not run manually.
setup
A setup command for configuring claude-mini-hud as Claude Code's terminal status line. It lets the user choose Chinese, English, minimal, or ultra-minimal display text and writes the setting to Claude Code's configuration.