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 instructions/messense/pi-parallel-agents/agents-mdgit clone --depth 1 https://github.com/messense/pi-parallel-agentsWhat 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.02010 | $0.02010 |
| Opus 5 | $0.01005 | $0.01005 |
| Sonnet 5 | $0.00402 | $0.00402 |
| Haiku 4.5 | $0.00201 | $0.00201 |
Grade A, and why
pi-parallel-agents AGENTS.md 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.
How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidelines for AI agents working on this codebase.
Project Overview
pi-parallel-agents is a pi extension that enables dynamic parallel execution of multiple agents with different models. This tool supports both:
- Inline configuration: Specify model, tools, thinking level, and system prompts per task
- Agent references: Reference existing agent definitions from
~/.pi/agent/agentsor.pi/agents
Architecture
src/
├── index.ts # Main extension entry point, tool registration, mode dispatch
├── executor.ts # Subprocess execution, spawns `pi --mode json` processes
├── parallel.ts # Concurrency utilities (worker pool, race with abort)
├── dag.ts # DAG engine for team mode (build, validate, execute task graphs, iterative review loops)
├── workspace.ts # Shared workspace for team artifact exchange
├── render.ts # TUI rendering for progress and results
├── types.ts # TypeScript types and Typebox schemas
├── agents.ts # Agent discovery and configuration resolution
└── context.ts # Context building (files, git info)
Key Design Decisions
-
Subprocess-based execution: Each task spawns a separate
piprocess with--mode jsonto capture structured output. This provides isolation and allows different models/configs per task. -
State in tool details: Results are stored in the tool result
detailsfield, which pi automatically persists. This enables session branching/restore without additional state management. -
Streaming progress: Uses
onUpdatecallback to emit progress during execution. The TUI shows real-time tool calls and partial output from running tasks. -
Hybrid agent model: Users can specify model/tools/thinking inline OR reference existing agents. When an agent is referenced, its settings are used as defaults and inline parameters override them.
-
Agent discovery: Agents are discovered from
~/.pi/agent/agents/*.md(user-level) and optionally.pi/agents/*.md(project-level) based onagentScopeparameter.
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 · 216 lines · 2,010 tokens per session scan A 3411eacda08d
pi-parallel-agents AGENTS.md is an instructions file published in the GitHub repository messense/pi-parallel-agents (11 stars, last pushed 6mo ago), licensed MIT. It adds 2,010 tokens to every session, about $0.0100 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.