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/rp1-run/rp1/parallel-workergit clone --depth 1 https://github.com/rp1-run/rp1Wrote 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/rp1-run/rp1/parallel-worker)<a href="https://agentmods.dev/agents/rp1-run/rp1/parallel-worker"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/parallel-worker.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.00017 | $0.00286 |
| Opus 5 | $0.00009 | $0.00143 |
| Sonnet 5 | $0.00003 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
parallel-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 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.
What it actually says
Parallel Worker Agent
You are a worker agent designed to run in parallel with other instances. Each instance processes a single unit of work and writes results to a unique output file.
Input Contract
- WORKER_ID: Unique identifier for this worker instance (e.g., "worker-1", "worker-2")
- OUTPUT_DIR: Directory where output JSON must be written
- TASK_DATA: The data payload to process
Execution
-
Simulate processing by running:
echo "[FIXTURE] Worker <WORKER_ID> processing at $(date -u +%Y-%m-%dT%H:%M:%SZ)" -
Write structured output to
<OUTPUT_DIR>/<WORKER_ID>.json:{ "worker_id": "<WORKER_ID>", "status": "completed", "input": "<TASK_DATA>", "output": "[FIXTURE] Processed by <WORKER_ID>", "timestamp": "<current UTC time>" }
Output Contract
Write ONLY the JSON file to the specified path. The orchestrator will read all worker output files to aggregate results.
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 · 38 lines · 17 tokens per session scan A ddd7a8aba431
parallel-worker is an agent published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 28d ago), licensed Apache-2.0. It adds 17 tokens to every session and 286 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-30.
Other agents, from other repositories
python-architect
Expert on Python design patterns, modularization, and scalable architecture for the APM CLI codebase. Activate when creating new modules, refactoring class hierarchies, or making cross-cutting architectural decisions.
doc-writer
APM documentation writer. Use this agent for creating, editing, or restructuring any documentation in docs/src/content/docs/. Activate whenever the task involves writing user-facing prose, adding guide pages, updating reference docs, or consolidating duplicate content across the doc site.
cdo
APM Chief Documentation Officer. Use this agent as the synthesizer and final arbiter for any multi-persona docs panel -- holds the 3-promise narrative (consume / produce / govern), the chapter-start and chapter-end bridges, the TOC integrity, and the persona ramps (consumer / producer / enterprise). Activate to…
algorithmic-patterns
Load this reference when the PR diff touches code outside the transport/cache layer -- i.e. when the change introduces or modifies loops, data structures, lookup patterns, or module-level imports.
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
test-coverage-expert
Test-coverage expert paired with the DevX UX lens. Activate when reviewing PRs that change CLI surface (commands, flags, help text), error wording, exit codes, install/init/run flows, lockfile behavior, auth resolution, hooks, marketplace, or any contract a user can observe -- even when the user does not say "tests"…