obsidian-hybrid-search: Skill for Claude Code

.ai/skills/dispatching-parallel-agents/SKILL.md

dispatching-parallel-agents is a skill for Claude Code, Codex from flowing-abyss/obsidian-hybrid-search. It costs 66 tokens per session (1,545 once invoked), scanned A, original, MIT.

A workflow for giving separate, isolated investigations to multiple coding agents when the tasks do not depend on one another. It is intended for diagnosis, research, or read-only checks, not simultaneous edits to the same working tree.

In plain words
What is it for?
Investigating separate test failures, examining unrelated subsystems, looking up documentation, or analysing independent problems in parallel.
Why use it?
It prevents unrelated investigations from blocking each other while avoiding file conflicts caused by parallel changes in one checkout. A working tree is the set of files currently checked out for a project.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

This is flowing-abyss/obsidian-hybrid-search's own configuration. It tells Claude Code and Codex how to work on obsidian-hybrid-search itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything obsidian-hybrid-search configures →

Reuse

Borrowing it

Nothing to install: this file belongs to flowing-abyss/obsidian-hybrid-search. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/flowing-abyss/obsidian-hybrid-search/master/.ai/skills/dispatching-parallel-agents/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/flowing-abyss/obsidian-hybrid-search

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for dispatching-parallel-agents

README.md
[![agentmods](https://agentmods.dev/badge/skills/flowing-abyss/obsidian-hybrid-search/dispatching-parallel-agents/github.svg)](https://agentmods.dev/skills/flowing-abyss/obsidian-hybrid-search/dispatching-parallel-agents)
Your own site
<a href="https://agentmods.dev/skills/flowing-abyss/obsidian-hybrid-search/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/flowing-abyss/obsidian-hybrid-search/dispatching-parallel-agents/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.

agentmods 80×15 button for dispatching-parallel-agents

Your own site · 80×15
<a href="https://agentmods.dev/skills/flowing-abyss/obsidian-hybrid-search/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/flowing-abyss/obsidian-hybrid-search/dispatching-parallel-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,545 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00066 $0.01545
Opus 5.5 $0.00026 $0.00618
Sonnet 5.5 $0.00013 $0.00309
Haiku 4.5 $0.00007 $0.00154

Measured today against content hash 47b94440cdc7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dispatching-parallel-agents 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 today.

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.

.ai/skills/dispatching-parallel-agents/SKILL.md · 191 lines

How it starts

The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dispatching Parallel Agents

Do not use for implementation plan tasks

This skill is for independent investigations: diagnosing unrelated test failures, read-only code investigation, documentation lookups, or analysis of independent subsystems , anything with no shared mutable state and no overlapping file changes. It is not for implementing tasks from one implementation plan in a shared working tree; running implementers in parallel there produces file conflicts. Use skill:subagent-driven-development for that , it dispatches one implementer at a time, with a review gate between tasks. Parallel implementation is only safe with per-task worktree isolation and a dedicated integration workflow, neither of which this skill provides.

Overview

You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history , you construct exactly what they need. This also preserves your own context for coordination work.

When you have multiple unrelated failures (different test files, different subsystems, different bugs), investigating them sequentially wastes time. Each investigation is independent and can happen in parallel.

Core principle: Dispatch one agent per independent problem domain. Let them work concurrently.

When to Use

digraph when_to_use {
    "Multiple failures?" [shape=diamond];
    "Are they independent?" [shape=diamond];
    "Single agent investigates all" [shape=box];
    "One agent per problem domain" [shape=box];
    "Can they work in parallel?" [shape=diamond];
    "Sequential agents" [shape=box];
    "Parallel dispatch" [shape=box];

    "Multiple failures?" -> "Are they independent?" [label="yes"];
    "Are they independent?" -> "Single agent investigates all" [label="no - related"];
    "Are they independent?" -> "Can they work in parallel?" [label="yes"];
    "Can they work in parallel?" -> "Parallel dispatch" [label="yes"];
    "Can they work in parallel?" -> "Sequential agents" [label="no - shared state"];
}

Read the full file on GitHub · 191 lines

Changes

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.

  1. today First seen · 191 lines · 66 tokens per session scan A 47b94440cdc7

Subscribe to this mod's changes

dispatching-parallel-agents is a skill published in the GitHub repository flowing-abyss/obsidian-hybrid-search (113 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,545 once invoked, about $0.0003 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-10-24.

Related

Other skills, from other repositories

wiki-lint

Run a deterministic, read-only health check on an Obsidian wiki. Use for lint, vault health check, audit wiki health, find orphans, find dead links, frontmatter audit, provenance audit, or wiki audit. Reports graph, link, frontmatter, provenance-ledger, empty-section, and stale-index findings; it does not reason…

AgriciDaniel/claude-obsidian · 79 tokens

code-understand

Map the load-bearing files, symbols, callers, and dependencies of an unfamiliar codebase before making changes. Use for architecture orientation, impact analysis, what-would-break questions, or finding callers. Uses CodeGraph when available and a dependency-free builtin fallback.

Ar9av/obsidian-wiki · 55 tokens

vs-search-tuning-partial-case

Use when the user provides 1-50 concrete bad-case search queries for one Viking Search app and wants local deterministic fixes. This skill only verifies request-level fine-operation interventions against a read-only baseline scene and delivers a console-ready configuration sheet, validated payloads, and a replay…

volcengine/SearchCLI · 85 tokens

misakanet-failure-memory

Search and record failure-recovery lessons from real engineering sessions; submit and verify debugging lessons across the MisakaNet network.

Ikalus1988/MisakaNet · 31 tokens

api-errors

McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.

cyanheads/obsidian-mcp-server · 54 tokens

report-issue-framework

File a bug or feature request against @cyanheads/mcp-ts-core when you hit a framework issue. Use when a builder, utility, context method, or config behaves contrary to the documented API — not for server-specific application bugs.

cyanheads/obsidian-mcp-server · 52 tokens