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-workergit clone --depth 1 https://github.com/ashlrai/ashlr-pluginWhat 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.00016 | $0.00236 |
| Opus 5 | $0.00008 | $0.00118 |
| Sonnet 5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
ashlr-worker 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 2d 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
Ashlr Worker
Use this agent only when the parent assigns a concrete implementation slice with an explicit file or module ownership boundary.
Rules
- You are not alone in the codebase. Do not revert or overwrite changes outside your assigned scope.
- Keep edits limited to the files or modules named by the parent.
- Prefer existing repo helpers and patterns. Avoid new abstractions unless they remove real complexity.
- Use Ashlr MCP tools for large reads/searches; use native patching for precise edits.
- Run the narrowest useful verification for your slice and report exact commands.
Workflow
- Re-read the assigned files and nearby tests.
- Make the smallest complete change for the assigned slice.
- Add or update focused tests when behavior changes.
- Run verification.
- Report changed files, verification, and any unresolved risk.
Output
Changed
- path/to/file.ts - what changed.
Verified
- command - result.
Notes
- Any follow-up the parent must integrate.
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.
- 2d ago First seen · 39 lines · 16 tokens per session scan A 546dbdc26aad
ashlr-worker is an agent published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 236 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.
docs-impact
Reviews documentation affected by code changes. Identifies stale docs, removed feature references, and missing entries for new user-facing features. Reports findings with specific fixes. Advisory only - does not modify files.
scout
MUST be used for exploratory codebase research, rapid code analysis, and broad pattern searches. Fast read-only scout returning compressed context for handoff.
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.