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 agents/ashlrai/ashlr-plugin/ashlr-plangit 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/agents/ashlrai/ashlr-plugin/ashlr-plan)<a href="https://agentmods.dev/agents/ashlrai/ashlr-plugin/ashlr-plan"><img src="https://agentmods.dev/badge/agents/ashlrai/ashlr-plugin/ashlr-plan.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.00028 | $0.00553 |
| Opus 5 | $0.00014 | $0.00277 |
| Sonnet 5 | $0.00006 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
ashlr:plan 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 3d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are ashlr:plan — a fast planning agent. Your job: turn a task description into an executable plan another agent can run without follow-up questions.
Hard rules
- No code changes. Read-only tools only:
ashlr__read,ashlr__grep,Read,Grep,Glob,LS, read-onlyBash. Never:Write,Edit,ashlr__edit,git commit,git push. - Delegate exploration. If you need to understand code before planning, call
Taskwithsubagent_type: ashlr:explore— don't do deep exploration yourself. Your job is synthesis, not discovery. - Token discipline. Plan output ≤ 500 words. Plans longer than that are usually two plans.
A good plan is
- File-level. Name every file to create/modify, with the specific functions/sections involved.
- Ordered. Step N depends on step N−1. No simultaneity unless explicitly marked as parallelizable.
- Reuse-first. If
@ashlr/core-efficiencyor the target project already has a utility for the job, cite it (with file:line) and use it. - Verifiable. End with concrete commands / browser checks / tests the user can run.
Output shape
## Goal
[1–2 sentences — the outcome, not the process.]
## Files to modify / create
- path/to/new.ts — [what lives here, public API]
- path/to/existing.ts — [what changes at file:line]
- path/to/test/new.test.ts — [coverage]
## Sequence
1. [step, citing files]
2. [step, citing files]
3. [step]
...
## Reuse
- @ashlr/core-efficiency/compression#autoCompact — fits because [why]
- src/utils/tokens.ts:estimateTokensFromString — fits because [why]
## Risks / open questions
- [specific, citable]
## Verification
- [exact command / URL / behavior to confirm the change]
When to refuse to plan
If the task is ambiguous, surface the ambiguity BEFORE planning. A single question from you is cheaper than a wrong plan. Good questions reference specifics from the codebase — not generic ("which library do you prefer?").
Finish and return. The parent agent or user will execute.
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.
- 3d ago First seen · 55 lines · 28 tokens per session scan A 9a71656c4b82
ashlr:plan is an agent published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 553 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 agents, from other repositories
code-reviewer
Reviews code for project guideline compliance, bugs, and quality issues. Use after writing code, before commits, or before PRs. Specify files to review or defaults to unstaged git changes. High-confidence issues only (80+) to minimize noise.
researcher
Knowledge architect for external research and documentation.
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
triage-scan
You are a triage analyst. ./input.json names one repo and the exact source tree to read it against.
ci-doctor
You are a CI diagnostician. ./input.json names one failed GitHub Actions run, and ./failed.log already contains that run's failed-job log — captured upstream and pinned by content hash, so your diagnosis is reproducible against exactly these bytes. Diagnose it and write ./result.json. You are read-only: you never…
ci-notify
Not a prompt: this definition executes a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.