ashlr-parallelize

A command that starts one sub-agent per file to apply the same instruction in parallel, then combines their results into one report. With the optional code mode, the sub-agents can make edits instead of only exploring files.

In plain words
What is it for?
Running the same analysis or code task over multiple files at once and merging the outcomes.
Why use it?
It reduces the time and repetition involved in applying the same review or change across many files.

Command

Install

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.

agentmods
npx agentmods add commands/ashlrai/ashlr-plugin/ashlr-parallelize
Clone the repo
git clone --depth 1 https://github.com/ashlrai/ashlr-plugin
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 709 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00032 $0.00709
Opus 5 $0.00016 $0.00354
Sonnet 5 $0.00006 $0.00142
Haiku 4.5 $0.00003 $0.00071

Measured 2d ago against content hash 53a62ae2c3b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

commands/ashlr-parallelize.md · 64 lines

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, use ashlr:ashlr:code (sonnet) agents instead of the default ashlr:ashlr:explore (haiku) agents. Use --code when 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

  1. Parse $ARGUMENTS:

    • Detect --code flag (remove from argument list before further parsing).
    • Determine subagent_type: ashlr:ashlr:code if --code, else ashlr: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] ..."
  2. 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.
    
  3. Spawn all agents in parallel via the Agent tool — one per file — each with subagent_type as determined in step 1.

  4. Wait for all agents to complete.

  5. Print merged report:

    ## /ashlr-parallelize — <N> agents · task: <task>
    
    ### <file1>
    <agent 1 output>
    
    ### <file2>
    <agent 2 output>
    
    ---
    Agents: <N> · subagent_type: <type> · files: <list>
    

Read the full file on GitHub · 64 lines

Changes

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.

  1. 2d ago First seen · 64 lines · 32 tokens per session scan A 53a62ae2c3b9

Subscribe to this mod's changes

ashlr-parallelize is a command published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 709 once invoked, about $0.0002 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.