dispatch-exploration

dispatch-exploration is a skill for Claude Code, Codex from ethanaubuchon/dossier-tradecraft. It costs 85 tokens per session (2,594 once invoked), scanned A, original, MIT.

A research-routing routine that sends a small group of questions to either stored project information or web research, then combines the findings. It can also ask for consent to verify web findings across sources.

In plain words
What is it for?
Use it during research or other workflows that need several questions answered from project records or the internet.
Why use it?
It removes the need to decide manually how each research question should be handled. Parallel queries can gather related information together while the verification step helps check web results.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it during research or other workflows that need several questions answered from project records or the internet.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ethanaubuchon/dossier-tradecraft/dispatch-exploration
Install

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.

Any agent
npx skills add ethanaubuchon/dossier-tradecraft --skill dispatch-exploration
Clone the repo
git clone --depth 1 https://github.com/ethanaubuchon/dossier-tradecraft

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 dispatch-exploration

README.md
[![agentmods](https://agentmods.dev/badge/skills/ethanaubuchon/dossier-tradecraft/dispatch-exploration/github.svg)](https://agentmods.dev/skills/ethanaubuchon/dossier-tradecraft/dispatch-exploration)
Your own site
<a href="https://agentmods.dev/skills/ethanaubuchon/dossier-tradecraft/dispatch-exploration"><img src="https://agentmods.dev/badge/skills/ethanaubuchon/dossier-tradecraft/dispatch-exploration/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 dispatch-exploration

Your own site · 80×15
<a href="https://agentmods.dev/skills/ethanaubuchon/dossier-tradecraft/dispatch-exploration"><img src="https://agentmods.dev/badge/skills/ethanaubuchon/dossier-tradecraft/dispatch-exploration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,594 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.00085 $0.02594
Opus 5 $0.00043 $0.01297
Sonnet 5 $0.00017 $0.00519
Haiku 4.5 $0.00009 $0.00259

Measured 12d ago against content hash 25f482caf06c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

dispatch-exploration 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 12d 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.

skills/dispatch-exploration/SKILL.md · 186 lines

How it starts

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

Dispatch Exploration

Send a small batch of research queries to specialist agents in parallel, apply the cross-verify consent gate when a returned finding triggers it, and return a compressed findings list.

Input

A list of query objects:

[
  {"question": "what does Ethan want re: relocation healthcare costs?", "target": "vault", "hint": "projects/relocation"},
  {"question": "current state of Spain non-lucrative visa for US remote workers", "target": "web"}
]
  • target"vault" or "web". Required.
  • hint (vault only) — optional slug-prefix scope to focus the search.

The input shape is stable — callers do not need to opt into the cross-verify gate; it is always on for target: "web" results.

Process

  1. Dispatch one agent per query, all in parallel (single message, multiple Agent tool calls):

    • target: "vault"vault-researcher
    • target: "web"web-researcher
  2. Wait for all results.

  3. Cross-verify intercept for each web result. See Cross-verify orchestration below. This is the only step where this skill may pause for user interaction; vault results are pass-through.

  4. Build a compressed findings list, one line (or short block) per query:

    Vault result:

    <query> → <slug> — <relevance> — <excerpt>
    

    or <query> → no match if the agent returned none.

    Web result (default):

    <query> → <summary> — <top 1-2 citations> — cohort: <cohort_spread> — flags: <flag list>
    

    Pass through cohort_spread and flags when present. Omit the cohort: / flags: segments when the agent returned no flags and a single-cohort spread (e.g. an evergreen-fact lookup with a clean sample).

    Web result (pricing mode, single tier):

    <query> → new: median $Y, range $A–$B (N reputable sources) — flags: <flags>
    

    Web result (pricing mode, tiered after consent):

    <query>
      new:  median $Y, range $A–$B (N sources, manufacturer-direct + major-retailer)
      used: median $Z, range $C–$D (M sources, marketplace-used / refurbished / etc.)
      flags: <flags>
    

Read the full file on GitHub · 186 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. 12d ago First seen · 186 lines · 85 tokens per session scan A 25f482caf06c

Subscribe to this mod's changes

dispatch-exploration is a skill published in the GitHub repository ethanaubuchon/dossier-tradecraft (3 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 2,594 once invoked, about $0.0004 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-31.

Related

Other skills, from other repositories

aidex-backlog

Use when the user wants to capture or defer something for later without acting on it now, or to work the existing backlog as a board. Fires on "add to the backlog", "add to the backlog the idea of X", "park this for later", "defer this one", "shelve the X idea", "queue this for later", "track this for later", "we'll…

yacb2/aidex · 214 tokens

aidex-audit

Use when the user wants to assess the state of a feature, flow, or module — a UX, security, performance, or accessibility audit; cataloging bugs, gaps, and opportunities; retesting open findings; escalating a finding to the backlog; or updating audit methodology. Fires on "I want to do a UX / security / performance /…

yacb2/aidex · 189 tokens

aidex-conventions

NOT auto-invoked. Shared documentation-canon hub for the aidex- family — holds the .context/ convention references (references/.md) that the single-purpose sibling skills delegate into. Routing — plan multi-step work → aidex-plan; record a decision/ADR → aidex-decision; capture a stakeholder/client request →…

yacb2/aidex · 157 tokens

aidex-plan

Use when implementation work should become a written .context/ plan before coding starts — either multi-phase work (a feature build, a migration, a refactor spanning backend/frontend/infra) or a single scoped change where only the file list and acceptance criteria need pinning down; a triage step picks which. Fires on…

yacb2/aidex · 218 tokens

aidex-review

Use when the user wants code reviewed as it stands — a module, a feature, a path, or the whole app — rather than a diff or a pull request. Covers correctness/bug hunting, simplification and dead code, exploitable security defects, and performance waste, and it first proposes which finder agents are worth launching and…

yacb2/aidex · 204 tokens

aidex-worktree

Use when the user wants to create, run or tear down a git worktree with its own isolated environment (database, ports, containers), or when a project has no worktree setup yet and one needs bootstrapping by investigating the repo topology and verifying the compose stack can run twice — "set up a worktree for X"…

yacb2/aidex · 186 tokens