A repository setup workflow that creates a shared development harness for context, rules, tools, and standards. A repository is a project's code and documentation store; this gives its contributors and coding agents a common set of guidance and working surfaces.

Use it when starting a repository or standardising one, to create shared context files, coding rules, agent skills, tools, scripts, and design standards.

It prevents each contributor or agent from using a different understanding of the project's conventions. It also checks whether the shared setup is present and connected to the repository's workflows.

drydock — Skill for Claude Code by naimkatiman/continuous-improvement

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 naimkatiman/continuous-improvement --skill drydock

Clone the repo

git clone --depth 1 https://github.com/naimkatiman/continuous-improvement

Made for: Claude Code.

Or install oh-my-claudecode, the plugin that ships this one along with the rest of its 36 skills, 17 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/naimkatiman/continuous-improvement/drydock/github.svg)](https://agentmods.dev/skills/naimkatiman/continuous-improvement/drydock)

Your own site

<a href="https://agentmods.dev/skills/naimkatiman/continuous-improvement/drydock"><img src="https://agentmods.dev/badge/skills/naimkatiman/continuous-improvement/drydock/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/naimkatiman/continuous-improvement/drydock"><img src="https://agentmods.dev/badge/skills/naimkatiman/continuous-improvement/drydock.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,163 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 92% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00084	$0.04163
Opus 5.5	$0.00034	$0.01665
Sonnet 5.5	$0.00017	$0.00833
Haiku 4.5	$0.00008	$0.00416

Measured 2mo ago against content hash e8d20ed2b25f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

drydock 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 2mo 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.

Origin

This is a copy

92% identical to drydock — 173 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

third-party/oh-my-claudecode/skills/drydock/SKILL.md · 338 lines

How it starts

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

Drydock

Lay the keel of the shipyard: one repo, one shared harness, every contributor inherits it. This skill scaffolds the environment that turns "everyone ships" into "everyone ships on the same design language" — it creates the 5 surfaces, seeds them minimally, wires them to the flows that fill them (launch writes CONTEXT/ADR; the launch C5 sediment pass and reviews sediment standards), and reports what exists, what was created, and what stays empty on purpose.

The four pillars and where they physically live:

Pillar	Surfaces
Context (shared background)	`CONTEXT.md` (glossary) + `docs/business/` + `docs/adr/` + OMC wiki
Rules (boundaries)	`CLAUDE.md` (thin entry: conventions, principles, index) + `docs/standards/`
Tools (composable capability)	`.omc/skills/` + `.mcp.json` + `scripts/`
Standards (the classification society)	`design-system/` (tokens, components, patterns) + `docs/standards/`

Metaphor map: the shipyard is the shared facility; the classification society (docs/standards/ + design-system/) sets the rules a ship must pass to be seaworthy; drydock lays the keel; launch ships it.

When to Use

starting a repo that humans and agents will both build on
a repo where knowledge lives in people's heads and chat history instead of files
onboarding: a new teammate or agent should inherit context by reading, not by asking

When Not to Use

throwaway prototypes with no collaborators
a repo already running this harness (use --check instead)

Workflow

1. Detect (never clobber)

Inventory what exists before writing anything:

CLAUDE.md present? AGENTS.md present? (rule: if either exists, extend it in place; create the missing one as a one-line pointer to the other; never create both fresh)
CONTEXT.md, docs/adr/, docs/standards/, docs/business/, design-system/, .omc/skills/, .mcp.json, scripts/, .gitattributes — which exist, which are missing?
OMC installed? — only worth checking when running inside an OMC session; outside one, skip this check silently (the harness works with or without OMC)

Read the full file on GitHub · 338 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.

2mo ago First seen · 338 lines · 84 tokens per session scan A e8d20ed2b25f

Subscribe to this mod's changes

drydock is a skill published in the GitHub repository naimkatiman/continuous-improvement (9 stars, last pushed 5d ago), licensed MIT. It adds 84 tokens to every session and 4,163 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to drydock, differing in 173 lines, and is treated as a copy.

Building agents Claude Code LLM Project management ai-agents coding-agents continuous-improvement hooks

drydock next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
drydocknaimkatiman/continuous-improvement	Skill	9	5d ago	MIT	A	84	Claude Code
opensrcvercel-labs/opensrc	Skill	3.0k	1mo ago	Apache-2.0	A	103	Claude Code
nopus-configureVistyy/nopus	Skill	302	2mo ago	MIT	A	27	Claude Code
agentproto-llm-endpointagentproto/ts	Skill	9	yesterday	Apache-2.0	A	77	Claude Code, Codex
agentpushagentproto/ts	Skill	9	yesterday	Apache-2.0	A	119	Claude Code, Codex
bureauagentproto/ts	Skill	9	yesterday	Apache-2.0	A	131	Claude Code, Codex
ap-workflowsagentproto/ts	Skill	9	yesterday	Apache-2.0	A	85	Claude Code, Codex