settings

A command for viewing or changing Shipyard workflow settings, stored in a project’s .shipyard/config.json file.

In plain words
What is it for?
Use it to list settings, inspect one setting, update a value, or view the current workflow configuration.
Why use it?
It avoids manually searching configuration files and shows whether a Shipyard project exists before changing settings.

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/settings
Clone the repo
git clone --depth 1 https://github.com/lgbarn/shipyard
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,273 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.00007 $0.02273
Opus 5 $0.00003 $0.01137
Sonnet 5 $0.00001 $0.00455
Haiku 4.5 $0.00001 $0.00227

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

Security

Grade A, and why

settings 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/settings.md · 235 lines

How it starts

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

/shipyard:settings - Workflow Settings

You are executing the Shipyard settings workflow. Follow these steps precisely.

Step 1: Check State Exists

Verify .shipyard/config.json exists. If not, tell the user:

"No Shipyard project found. Run /shipyard:init first to create a project and configure settings."

Then stop.

Step 2: Read Current Settings

Read .shipyard/config.json and parse all fields.

Step 3: Determine Mode

Check if the user provided arguments:

  • No arguments — proceed to Step 4 (interactive mode).
  • list — proceed to Step 5 (display all settings).
  • A single key name (e.g., security_audit, model_routing.building) — proceed to Step 6 (display one setting).
  • A key name followed by a value (e.g., security_audit false, context_tier minimal) — proceed to Step 7 (set one setting).

Step 4: Interactive Mode

Display current settings as a readable summary:

Shipyard Settings (.shipyard/config.json)

Workflow:
  Interaction mode:  {interaction_mode}
  Git strategy:      {git_strategy}
  Review depth:      {review_depth}

Quality Gates:
  Security audit:         {security_audit}
  Simplification review:  {simplification_review}
  IaC validation:         {iac_validation}
  Documentation:          {documentation_generation}

Model Routing:
  Architecture:    {model_routing.architecture}
  Building:        {model_routing.building}
  Review:          {model_routing.review}
  Planning:        {model_routing.planning}
  Validation:      {model_routing.validation}
  Security audit:  {model_routing.security_audit}
  Simplification:  {model_routing.simplification}
  Documentation:   {model_routing.documentation}
  Mapping:         {model_routing.mapping}
  Debugging:       {model_routing.debugging}

Context:
  Context tier:        {context_tier}
  Codebase docs path:  {codebase_docs_path}

Then use AskUserQuestion to ask: "Which settings category would you like to change?"

  • Workflow — Interaction mode, git strategy, review depth
  • Quality gates — Security audit, simplification, IaC validation, documentation
  • Model routing — Model assignments per agent role
  • Context — Context tier and codebase docs path

Read the full file on GitHub · 235 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 · 235 lines · 7 tokens per session scan A b6d214507b0d

Subscribe to this mod's changes

settings is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 2,273 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.