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 rules/golid-ai/golid/parallel-subagentsgit clone --depth 1 https://github.com/golid-ai/golidWrote 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/rules/golid-ai/golid/parallel-subagents)<a href="https://agentmods.dev/rules/golid-ai/golid/parallel-subagents"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/parallel-subagents.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.00033 | $0.01156 |
| Opus 5 | $0.00016 | $0.00578 |
| Sonnet 5 | $0.00007 | $0.00231 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
parallel-subagents 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Subagents for Multi-File Operations
Thesis: Sequential edits across many files waste time and lose context. Split independent work across subagents, verify after completion.
When to invoke
- 5+ independent files — auditing or editing across many files with no ordering dependencies between them
- User request — the user explicitly asks to run work in parallel or use subagents
- Plan parallel slices —
plan-execution-loopdispatches parallel implement subagents for a multi-file slice
When a task involves auditing or editing 5+ independent files, prefer parallel subagents over sequential tool calls. If changes have ordering dependencies, keep dependent steps sequential.
When to parallelize
- Audits: searching for patterns, checking consistency, or reviewing code across 5+ files
- Edits: renaming, fixing stale references, or applying the same pattern across 5+ files
- Mixed: audit first (parallel), then edit (parallel) based on findings
How to split work
Group files by independence — changes that don't depend on each other go in separate subagents. Max 4 concurrent subagents.
Good splits:
- By layer: Docker/infra files | source code | documentation | config
- By concern: backend changes | frontend changes
Bad splits:
- Putting a TSX file and its CSS file in different subagents (coordinated rename)
- Splitting a function definition from its callers
Pre-flight: predict shared-file collisions
Before dispatching, rg the plans/specs for file paths each subagent will touch. Flag any file appearing in 2+ subagents — typically openapi.yaml, module spec.md files, shared type files (frontend/src/lib/api.ts, frontend/src/lib/constants.ts), barrels, internal/wire/routes.go. These cause cherry-pick conflicts.
For each shared file, decide upfront: which subagent owns which section? Tell each subagent explicitly to make additive edits (new sections, new contiguous blocks) and not restructure unrelated content. Textual diffs that touch different lines in the same file merge cleanly; restructured files do not.
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 · 72 lines · 33 tokens per session scan A 9a98c868e2d5
parallel-subagents is a cursor rule published in the GitHub repository golid-ai/golid (40 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 1,156 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-30.
Other cursor rules, from other repositories
adapter-features
Database-specific features must be implemented in the specialized adapter only. Base adapters (postgres, mysql, etc.) must remain database-agnostic.
unit-tests-tdd
TDD required for behavior changes; ≥80% package coverage on touched packages; unit-test conventions.
integration-tests
Human-readable integration test requests; helpers vs httptest; suites/ vs per-DB placement.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
cursorrules
This file is intentionally short. Use AGENTS.md as the source of truth.
refactoring-skill
Cursor rule "refactoring-skill" from KaelSensei/MagicAIBuilder, covering refactoring skill, principles, techniques, safety and cursor behavior.