quick

A command for running a small, self-contained coding task with a defined Shipyard workflow.

In plain words
What is it for?
Use it for focused changes that can be completed in one effort and do not require broad architectural work.
Why use it?
It provides a lightweight way to check the project state and record the task without setting up the full planning process.

Command

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.

agentmods
npx agentmods add commands/lgbarn/shipyard/quick
Clone the repo
git clone --depth 1 https://github.com/lgbarn/shipyard
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,026 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00008 $0.01026
Opus 5 $0.00004 $0.00513
Sonnet 5 $0.00002 $0.00205
Haiku 4.5 $0.00001 $0.00103

Measured 2d ago against content hash e549e82c6aa8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

commands/quick.md · 129 lines

How it starts

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

/shipyard:quick - Quick Task Execution

You are executing the Shipyard quick task workflow. This is for small, self-contained tasks that don't need the full phase/plan/build cycle but still benefit from structured execution.

Step 1: Validate State

Check if .shipyard/ exists.

  • If it exists: Read STATE.json for context. Proceed normally.
  • If it does not exist: Create a minimal .shipyard/ setup:
    • Create .shipyard/STATE.json and .shipyard/HISTORY.md with minimal content
    • Create .shipyard/quick/ directory
    • This is acceptable for quick tasks -- no full init required.

Step 2: Capture Task Description

  • If a task description was provided as an argument, use it.
  • If no argument was provided, ask the user:

    "What task would you like to execute? Describe it in one or two sentences."

Validate the task is appropriate for quick mode:

  • Should be completable in a single focused effort
  • Should not require architectural changes
  • Should not span multiple files in unrelated areas

If the task seems too large, suggest:

"This task seems substantial. Consider using /shipyard:init and /shipyard:plan for better structure. Continue with quick mode anyway? (y/n)"

Step 3: Generate Sequential Number

Look in .shipyard/quick/ for existing quick task files. Generate the next sequential number:

  • First task: 001
  • Format: zero-padded 3-digit number

Step 4: Detect Working Directory & Model Routing

Follow Worktree Protocol (detect if running in a git worktree; if so, use worktree root for paths and record the branch name; see docs/PROTOCOLS.md) -- detect worktree, record working directory and branch. Follow Model Routing Protocol (select the correct model for each agent role using model_routing from config; see docs/PROTOCOLS.md) -- read model_routing from config for agent model selection.

Step 5: Quick Plan

Dispatch an architect agent (subagent_type: "shipyard:architect") in quick mode with context per Agent Context Protocol (pass PROJECT.md, config.json, working directory, branch, and worktree status to all agents; see docs/PROTOCOLS.md):

  • The task description
  • Codebase docs per Codebase Docs Protocol (resolve configured codebase docs path and load CONVENTIONS.md, STACK.md, ARCHITECTURE.md, etc.; see docs/PROTOCOLS.md)

Read the full file on GitHub · 129 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. 2d ago First seen · 129 lines · 8 tokens per session scan A e549e82c6aa8

Subscribe to this mod's changes

quick is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 1,026 once invoked, about $0.0000 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.