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/acendas/shipyard/dispatching-research-tasknpx skills add Acendas/shipyard --skill dispatching-research-taskgit clone --depth 1 https://github.com/Acendas/shipyardWhat 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.00015 | $0.01913 |
| Opus 5 | $0.00008 | $0.00957 |
| Sonnet 5 | $0.00003 | $0.00383 |
| Haiku 4.5 | $0.00002 | $0.00191 |
Grade A, and why
dispatching-research-task 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dispatching a Research Task
Render before asking. Before any AskUserQuestion, render the decision context as assistant chat text. Content that exists only in a Read result, a subagent/Agent return, or the question/option strings does not count as rendered (the UI shows a compact card) — restate it in chat first.
A kind: research task answers a question. Its deliverable is a markdown findings doc, not code. The subagent reads (codebase, web, docs), reasons, and writes a single output file. Wrong dispatch → silent-pass bug: feature builders have no Red step for a research-shaped task and exit clean on an empty tree, satisfying the "Before Exiting" gate trivially. Route here.
When to Invoke
/ship-execute calls this skill when a task's frontmatter has kind: research. Other entry points:
/ship-discussmay invoke this for an inline technical investigation during feature shaping ("which JWT library should we use?")./ship-sprintmay invoke this during planning when a feature can't be specced without a design tradeoff analysis.
Per the action items, the routing decision (kind: feature vs operational vs research) lives in the calling command skill. This skill assumes the routing already chose research.
Inputs
task_id— e.g.,R-013(research tasks conventionally useR-prefix, but any ID works).task_file_path— absolute path under<SHIPYARD_DATA>/spec/tasks/.parent_feature_path— absolute path or null.data_dir— literal<SHIPYARD_DATA>path.findings_dir—<SHIPYARD_DATA>/research/(computed; the only writable area).expected_findings_filename— derived from task ID + slug, e.g.,R-013-jwt-library-evaluation.md.
Dispatching the Researcher
The researcher methodology (the write-scope hard gate, the reading list, the
findings-doc template, when-to-stop, and the Required Return Shape) lives in
the registered agent agents/shipyard-researcher.md — read it once if you
need to know exactly what it does; do not re-inline it here.
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 · 114 lines · 15 tokens per session scan A 3c16716a3356
dispatching-research-task is a skill published in the GitHub repository Acendas/shipyard (2 stars, last pushed 20d ago), licensed MIT. It adds 15 tokens to every session and 1,913 once invoked, about $0.0001 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.
Other skills, from other repositories
engenharia-de-requisitos
Use when doing requirements engineering, business analysis, or the software-engineering stage of discovering / specifying / validating / managing requirements — the stage BEFORE code (what to build) and AFTER (was the right thing built?), for new projects and for evolutions of existing ones. Triggers (EN)…
engenharia-de-requisitos
Use when doing requirements engineering, business analysis, or the software-engineering stage of discovering / specifying / validating / managing requirements — the stage BEFORE code (what to build) and AFTER (was the right thing built?), for new projects and for evolutions of existing ones. Triggers (EN)…
write-epic
Produces a complete epic definition following Atlassian agile guidance. An epic captures a large initiative that is too big for a single sprint and must be decomposed into user stories.
write-user-story
Produces a complete, ready-to-groom user story following the standard Atlassian/agile format. It applies the INVEST criteria and the 3 Cs framework (Card, Conversation, Confirmation) to ensure each story is well-scoped, valuable, and testable — not just syntactically correct.
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
agent-workspace-linux
Use when a task needs an isolated hidden Linux desktop or workspace-owned browser: GUI app QA, web/browser/shopping automation, sandboxed app observation, or stale workspace cleanup. Routes agent-workspace-linux MCP tools on demand. Does NOT apply to host desktop/Chrome control, generic MCP setup, or pure code/file…