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-eco-mode)<a href="https://agentmods.dev/commands/ashlrai/ashlr-plugin/ashlr-eco-mode"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-plugin/ashlr-eco-mode/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ashlrai/ashlr-plugin/ashlr-eco-mode"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-plugin/ashlr-eco-mode.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00796 |
| Opus 5.5 | $0.00010 | $0.00318 |
| Sonnet 5.5 | $0.00005 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
ashlr-eco-mode 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 1mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Toggle eco mode for the current session.
Usage
/ashlr-eco-mode on # enable eco mode
/ashlr-eco-mode off # disable eco mode
/ashlr-eco-mode status # show current eco mode state + active behaviors
What eco mode does
When ASHLR_ECO=1 is set, the following behaviors activate automatically:
| Behavior | Details |
|---|---|
| Auto-compact every 15 tool calls | Triggers /ashlr-compact automatically to prevent stale result accumulation |
| Force genome grep | Errors if .ashlrcode/genome/ is missing, with a link to /ashlr-genome-init |
| Lower summarization threshold | Reduces LLM summarization threshold from 16384 → 12288 bytes (fires more often) |
| Smart Task routing | Task tool calls without explicit subagent_type are routed to ashlr:ashlr:explore when the prompt is question-shaped (starts with what/where/how/find/explain/why/which/when/who) |
| Suppress image attachments | Image data in tool results is stripped before processing |
Auto-activate /ashlr-brief |
If ~/.ashlr/brief.json is unset or off, eco-mode-on writes level: standard and eco-mode-off restores the prior level. See /ashlr-brief for details. |
Environment variable
| Variable | Value | Effect |
|---|---|---|
ASHLR_ECO |
1 |
Eco mode on |
ASHLR_ECO |
unset / 0 |
Eco mode off |
The eco router hook (hooks/pretooluse-eco-router.ts) reads ASHLR_ECO and injects subagent_type: "ashlr:ashlr:explore" into question-shaped Task tool calls.
The status line shows a eco badge when ASHLR_ECO=1.
Steps
on
- Set env var via Bash:
export ASHLR_ECO=1 - Print:
Eco mode ON. Active behaviors: - Auto-compact every 15 tool calls - Force genome grep (error if .ashlrcode/genome/ missing) - Summarization threshold: 12288 bytes (was 16384) - Question-shaped Task calls routed to ashlr:ashlr:explore - Image attachments suppressed in tool results Run /ashlr-eco-mode off to disable.
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.
- 1mo ago First seen · 93 lines · 24 tokens per session scan A 70811ef6163e
ashlr-eco-mode is a command published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 796 once invoked, about $0.0001 per session on Opus 5.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
budget
Manage the token budget for Claude Code sessions. Model-aware — picks the right effective context window and prices per model. The session's REAL model is read from the transcript by the budget hook; config.model is only the fallback. Everything from Sonnet 4.6 up is 1M; Haiku 4.5 is 200K.
orchestrate
Do this task as an orchestrator. The aim is the same result at a fraction of the cost: in a long session, every token in this conversation is re-read on each later request, while a subagent's reading is discarded when it returns. The plugin's subagents run on Haiku 5.5, about 40× cheaper per token than Opus 5.5.
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
scout-work
Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).
ccc-status
Turn periodic progress updates for long sessions on or off, choose the channel (Slack, Discord, email or console), interval and detail level, or send one now. Use when the user asks to be kept posted, pinged on progress, or to stop updates.
ccc-teleport
Move work between devices: pull a Claude Code on the web session into this terminal with teleport, or keep a local session controllable from the web or mobile app with Remote Control. Use when switching device, monitoring a long task from a phone, or resuming a cloud session locally.