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-parallelize)<a href="https://agentmods.dev/commands/ashlrai/ashlr-plugin/ashlr-parallelize"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-plugin/ashlr-parallelize/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-parallelize"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-plugin/ashlr-parallelize.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.00032 | $0.00709 |
| Opus 5.5 | $0.00013 | $0.00284 |
| Sonnet 5.5 | $0.00006 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
ashlr-parallelize 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spawn one sub-agent per file, all running the same task in parallel, then merge their outputs.
Usage
/ashlr-parallelize <task> <file1> [file2] [file3] ... [--code]
<task>— the instruction to apply to each file (quoted string or unquoted phrase ending before the first file path).<file1> [file2] ...— one or more file paths (contain/or.or start with__).--code— optional flag. When present, useashlr:ashlr:code(sonnet) agents instead of the defaultashlr:ashlr:explore(haiku) agents. Use--codewhen the task requires edits; omit for read-only analysis.
Examples
/ashlr-parallelize "explain what this module exports" src/utils.ts src/helpers.ts src/types.ts
/ashlr-parallelize "find all TODO comments and summarize them" hooks/pretooluse-read.ts hooks/pretooluse-bash.ts
/ashlr-parallelize --code "add JSDoc to all exported functions" servers/read-server.ts servers/grep-server.ts
Steps
-
Parse
$ARGUMENTS:- Detect
--codeflag (remove from argument list before further parsing). - Determine
subagent_type:ashlr:ashlr:codeif--code, elseashlr:ashlr:explore. - Split remaining tokens: file-path-like tokens (contain
/,., or start with__) → file list; everything before the first file path → task string. - If no files are found, error: "No files specified. Usage: /ashlr-parallelize
<task><file1>[file2] ..." - If task string is empty, error: "No task specified. Usage: /ashlr-parallelize
<task><file1>[file2] ..."
- Detect
-
For each file, construct an agent prompt:
Task: <task> File: <file_path> Focus exclusively on this file. Do not read other files unless they are direct imports needed to answer the task. Keep your response under 300 words. Cite file:line for every claim. -
Spawn all agents in parallel via the Agent tool — one per file — each with
subagent_typeas determined in step 1. -
Wait for all agents to complete.
-
Print merged report:
## /ashlr-parallelize — <N> agents · task: <task> ### <file1> <agent 1 output> ### <file2> <agent 2 output> --- Agents: <N> · subagent_type: <type> · files: <list>
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 · 64 lines · 32 tokens per session scan A 53a62ae2c3b9
ashlr-parallelize is a command published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 709 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
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.
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…
ccc-orchestrate
Run a sequential multi-agent workflow (feature, bugfix, refactor, security or custom chain) with structured handoffs, plus optional tmux and worktree workers for long-running sessions. Use when a task needs planner, implementer and reviewer stages in order.
complete
Signal that a skill's work is complete. Triggers downstream subscriptions with "when": "complete" timing. Automatically invoked — do not run manually.
environment-switching-local-cloud-ssh
The environment selector at the bottom of Claude Code switches where work executes: local for fast interactive iteration, cloud (Anthropic servers) for routines that must run with your machine off, SSH for driving a remote box like a VPS.