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 skills add RobinNorberg/oh-my-copilot --skill drydockgit clone --depth 1 https://github.com/RobinNorberg/oh-my-copilotWrote 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.
[](https://agentmods.dev/skills/robinnorberg/oh-my-copilot/drydock)<a href="https://agentmods.dev/skills/robinnorberg/oh-my-copilot/drydock"><img src="https://agentmods.dev/badge/skills/robinnorberg/oh-my-copilot/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.
<a href="https://agentmods.dev/skills/robinnorberg/oh-my-copilot/drydock"><img src="https://agentmods.dev/badge/skills/robinnorberg/oh-my-copilot/drydock.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.04156 |
| Opus 5 | $0.00042 | $0.02078 |
| Sonnet 5 | $0.00017 | $0.00831 |
| Haiku 4.5 | $0.00008 | $0.00416 |
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 3d 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.
This is a copy
88% identical to drydock — 28 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.
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) | .omg/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
--checkinstead)
Workflow
1. Detect (never clobber)
Inventory what exists before writing anything:
CLAUDE.mdpresent?AGENTS.mdpresent? (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/,.omg/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)
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.
- 3d ago First seen · 338 lines · 84 tokens per session scan A 1711f47af762
drydock is a skill published in the GitHub repository RobinNorberg/oh-my-copilot (5 stars, last pushed 4d ago), licensed MIT. It adds 84 tokens to every session and 4,156 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to drydock, differing in 28 lines, and is treated as a copy.
Other skills, from other repositories
orchestrator-lanes
A file-based project-management playbook for a specific Claude Code development orchestrator. It organizes work into lanes, plans, dependency steps, validation phases, and shipping stages.
project-life
A system for keeping project ideas, tasks, plans, progress, decisions, and lessons in one place. A monorepo-style project workflow is implied, but the input does not define the storage format in full.
lane-contract
A file-based task contract system for describing coding tasks in YAML, including which files a task owns and how it must be checked.
seo-project-life
A guide to the files, commands, stages, and working process of an SEO project. SEO, or search-engine optimization, is the work of improving a site's visibility in search results.
resume-project
A project-resume skill for starting work on an existing repository after a pause or a new session. It reports the current state, blockers, and next actions.
drmax-brandcore
A company facts file and guided process for recording approved claims, products, legal details, and other information that content agents may use. It acts as a single source of truth instead of letting later content generation guess.