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 naimkatiman/continuous-improvement --skill drydockgit clone --depth 1 https://github.com/naimkatiman/continuous-improvementWrote 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/naimkatiman/continuous-improvement/drydock)<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.
<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>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 | $0.00042 | $0.02082 |
| Sonnet 5 | $0.00017 | $0.00833 |
| 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
92% identical to drydock — 0 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) | .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
--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/,.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)
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 e8d20ed2b25f
drydock is a skill published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed 4d ago), licensed MIT. It adds 84 tokens to every session and 4,163 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to drydock, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
pb-nested-orchestrator
Spawn a parent agent that spawns and supervises its own sub-agents, forming a two-level tree on the agentproto daemon. Trigger for delegation depth - 'agent that spawns sub-agents', 'two-level agent tree', 'let an agent orchestrate on its own'.
ap-tasks
Use the agentproto shared task board — taskcreate, taskclaim (CAS with rev), tasklist, and taskupdate to coordinate parallel agents on one board, gate done with verify commands, and hand off work claimably. Trigger when coordinating parallel agents, splitting work across sessions, handing off tasks, or needing…
supervise-long-missions
Route missions that outlive your attention — durable waiting, completion gates with retries, scheduled cron check-ins, shared task boards, spend tracking, and cleanup. Use when an agent works longer than one turn or you must not block on it. Triggers: supervise, long-running mission, check-in, non-blocking wait…
post-issue-comment
Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments.
tencent-meeting-mcp
A Tencent Meeting assistant for scheduling meetings and working with participants, recordings, transcripts, and AI-generated meeting notes.
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.