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 skills/youglin-dev/aha-loop/parallel-explorenpx skills add YougLin-dev/Aha-Loop --skill parallel-exploregit clone --depth 1 https://github.com/YougLin-dev/Aha-LoopWhat 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.00039 | $0.01754 |
| Opus 5 | $0.00019 | $0.00877 |
| Sonnet 5 | $0.00008 | $0.00351 |
| Haiku 4.5 | $0.00004 | $0.00175 |
Grade A, and why
parallel-explore 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Exploration Skill
Guide the process of exploring multiple implementation approaches simultaneously using git worktrees.
The Job
- Identify when parallel exploration would be valuable
- Define distinct approaches to explore
- Create isolated worktrees for each approach
- Execute exploration in parallel
- Evaluate and compare results
- Merge the best solution
When to Use Parallel Exploration
Good Candidates
- Architecture decisions - Different patterns (e.g., microservices vs monolith)
- Library selection - Comparing similar libraries hands-on
- Algorithm choices - Different approaches to the same problem
- API design - Different interface designs
- Performance optimization - Multiple optimization strategies
Not Worth Parallelizing
- Simple, clear-cut decisions
- Tasks with obvious single approach
- Very small changes
- Changes that don't warrant the overhead
Exploration Process
Step 1: Identify the Decision Point
When you encounter a significant decision:
## Decision Point Identified
**Question:** [What needs to be decided]
**Context:** [Why this matters]
**Approaches to Explore:**
1. [Approach A] - [Brief description]
2. [Approach B] - [Brief description]
3. [Approach C] - [Brief description]
**Exploration Value:** [Why parallel exploration helps here]
Step 2: Start Exploration
Use the parallel explorer script:
./scripts/aha-loop/parallel-explorer.sh explore "task description" --approaches "approach1,approach2,approach3"
Or let AI suggest approaches:
./scripts/aha-loop/parallel-explorer.sh explore "task description"
# AI will suggest approaches automatically
Step 3: Work in Each Worktree
In each worktree, the AI should:
- Implement fully - Not just a stub, but working code
- Write tests - Validate the approach works
- Document findings - Create EXPLORATION_RESULT.md
Step 4: Create Exploration Result
Each worktree must have EXPLORATION_RESULT.md:
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 · 335 lines · 39 tokens per session scan A 1d1014d73155
parallel-explore is a skill published in the GitHub repository YougLin-dev/Aha-Loop (181 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 1,754 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…