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-upgradegit 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-upgrade)<a href="https://agentmods.dev/commands/ashlrai/ashlr-plugin/ashlr-upgrade"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-plugin/ashlr-upgrade.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.00078 | $0.01086 |
| Opus 5 | $0.00039 | $0.00543 |
| Sonnet 5 | $0.00016 | $0.00217 |
| Haiku 4.5 | $0.00008 | $0.00109 |
Grade A, and why
ashlr-upgrade 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running the ashlr upgrade flow.
What Pro gives you
Your team learns together. Free ashlr builds a genome that lives on your machine and resets when you switch laptops. Pro lifts that genome into a shared encrypted layer so every engineer's discoveries become everyone's — across machines, across teammates, across sessions.
- Shared team genome — every
ashlr__grephit, every file pattern discovered, every codebase insight lands in an encrypted, versioned store the whole team retrieves from. New engineers onboard into context, not silence. - Weekly team digest — a summary of what the team learned that week: top genome sections hit, streak rankings, savings milestones. Delivered via
/ashlr-resume; optional email. - Cross-machine streak and savings sync — your streak counter, savings ledger, and
/ashlr-dashboardfollow you across machines without manual copy. - Cloud LLM summarizer —
ashlr__readand genome summarization run on hosted Haiku. No local Ollama or GPU setup required. - Hosted embedding retrieval —
ashlr__grepuses a cloud pgvector index refreshed on every push. Materially better recall on repos with > 5,000 files.
Pro: $12/mo or $120/yr — one developer, all cloud features.
Pro Team: $24/user/mo (min 3 seats) or $20/user/mo annual — shared encrypted genome, org-wide savings dashboard, policy packs (shipping), SSO.
First checkout includes a 7-day free trial — no charge until the trial ends, cancel any time. The free tier is never crippled; Pro adds cloud context, it does not remove anything free.
Invocation
Run the upgrade script:
bun run "${CLAUDE_PLUGIN_ROOT}/scripts/upgrade-flow.ts"
Stream its stdout verbatim to the user. Do not add narration between steps — the script output is the narrative.
Sign-in methods
The script will first ask how the user wants to sign in:
- Sign in with GitHub (primary) — opens
https://plugin.ashlr.ai/signinin the browser. After GitHub OAuth consent (read:user user:email public_repo), the CLI receives a token automatically. This also unlocks the repo picker for auto-genome builds on public repos. - Magic link (fallback) — sends a one-time sign-in link to the user's email. Use this if the user cannot open a browser or prefers not to connect GitHub.
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 · 97 lines · 78 tokens per session scan A 30726cefdd62
ashlr-upgrade is a command published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed 5d ago), licensed MIT. It adds 78 tokens to every session and 1,086 once invoked, about $0.0004 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 +…