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 skills add DojoGenesis/mcp --skill parallel-tracksgit clone --depth 1 https://github.com/DojoGenesis/mcpWrote 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/skills/dojogenesis/mcp/parallel-tracks)<a href="https://agentmods.dev/skills/dojogenesis/mcp/parallel-tracks"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/parallel-tracks/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/skills/dojogenesis/mcp/parallel-tracks"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/parallel-tracks.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.00041 | $0.01902 |
| Opus 5.5 | $0.00016 | $0.00761 |
| Sonnet 5.5 | $0.00008 | $0.00380 |
| Haiku 4.5 | $0.00004 | $0.00190 |
Grade A, and why
parallel-tracks 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Tracks Skill
Version: 1.0 Author: Tres Pies Design Purpose: Provide a structured, repeatable process for planning and executing large development tasks in parallel, significantly reducing timelines while improving focus and architectural discipline.
I. The Philosophy: From Sequence to Simultaneity
In complex software development, the default is sequential execution: one task must finish before the next can begin. This creates bottlenecks, extends timelines, and reduces cognitive focus. The Parallel Tracks Pattern is a shift from sequence to simultaneity.
This skill provides a framework for identifying natural boundaries within a large body of work and splitting it into independent, self-contained tracks that can be executed concurrently. It is not merely about doing things at the same time; it is a disciplined practice of upfront architectural planning, rigorous specification, and clear dependency management that makes parallel execution possible.
The math:
- Sequential: Track A (1 week) + Track B (1 week) + Track C (1 week) = 3 weeks
- Parallel: Track A + Track B + Track C (all 1 week) = 1 week
- Typical reduction: 50-70% when done correctly
II. When to Use This Skill
Use when ALL of these conditions are met:
- The task is large enough: >2 weeks of sequential work as a rule of thumb
- Clear separation of concerns exists: The work can be cleanly divided by layer, feature, or component
- Multiple agents or developers are available to work simultaneously
- Tracks have minimal dependencies on each other
- You are committed to writing self-contained specifications for each track
Do NOT use when:
- The task is small (<2 weeks sequential)
- The work is tightly coupled with no natural boundaries
- Only one agent/developer is available
- The specifications cannot be written independently
III. The 6-Step Workflow
Step 1: Identify Natural Boundaries
Analyze the total scope and find clean separation points. Target 2-4 substantial tracks.
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 · 230 lines · 41 tokens per session scan A 8b214c96747d
parallel-tracks is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 1,902 once invoked, about $0.0002 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 skills, from other repositories
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.
migrate-state-management
Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use when refactoring away from Redux/Context, moving state to the right store, or when the user asks to migrate state management.
lsp-implement
Find all concrete implementations of an interface or abstract type. Use when you need to know what types satisfy an interface, or what subtypes exist before changing a base type.
lsp-local-symbols
Fast file-scoped symbol analysis — find all usages of a symbol within the current file, list all symbols defined in the file, and get type info at a position. Use when you need local-scope analysis without a workspace-wide search.
Linux Malware Analysis
Expert ELF malware analysis — packing, toolchain ID, kill chain, persistence, C2, rootkits, cryptominers, Go/Rust/Mirai patterns, MITRE ATT&CK mapping.