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 harborgit 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/harbor)<a href="https://agentmods.dev/skills/robinnorberg/oh-my-copilot/harbor"><img src="https://agentmods.dev/badge/skills/robinnorberg/oh-my-copilot/harbor/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/harbor"><img src="https://agentmods.dev/badge/skills/robinnorberg/oh-my-copilot/harbor.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.00083 | $0.04478 |
| Opus 5.5 | $0.00033 | $0.01791 |
| Sonnet 5.5 | $0.00017 | $0.00896 |
| Haiku 4.5 | $0.00008 | $0.00448 |
Grade A, and why
harbor 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 23d 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 harbor — 2 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harbor
Harbor is the shipyard's intake. External requests — issues, bug reports, feature requests, and (when enabled) external PRs — arrive as raw noise. Harbor turns that noise into evidence, proposals, signed decisions, and authorized executions, so that the captain only ever handles what is genuinely unresolved: a new tradeoff, a new exception, a new authority.
Success order. First: zero overreach — nothing happens that nobody authorized. Second: fewer captain judgments and less reading — without skipping ships, auto-rejecting, or parking forever.
The four records
Every harbor action produces one of four records. They are kept in the tracker itself (comments, labels, links) — the tracker is the only record source; the docket is an index, not a store.
| Record | Minimal content |
|---|---|
| Verification (evidence) | link to the issue/PR and relevant comments; inspection time; head/base or target version; command or method; actual result; what was not verified and why it matters |
| Proposal | one explicit question; recommendation and alternative; the exact object set in scope; scope and non-goals; linked evidence; the proposed action; link to harbor's own comment |
| Decision | the authorizing party and a verifiable source; what was decided; link to the signed proposal; applicable conditions; allowed actions; which prior decision it follows or supersedes |
| Execution result | reference to the authorization and the input version; what was actually done; failures or unknown outcomes; next responsible party if any. Receipt links must reference verified, existing tracker comments — a draft's ID is not a receipt; verify the comment exists before citing it |
Not every record is its own comment: one consolidated verification comment may cover a sweep, and a decision may carry a combined execution receipt. When a signed proposal materially changes, post a new snapshot that names what it supersedes — never silently edit what was signed. If a cited source comment is later edited, re-verify validity before relying on it; tracker comments are not immutable storage.
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.
- 23d ago Changed · +8 lines 553bcf802e13
- 25d ago First seen · 170 lines · 83 tokens per session scan A da54bfb82955
harbor is a skill published in the GitHub repository RobinNorberg/oh-my-copilot (5 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 4,478 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to harbor, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
harbor
Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, impact and evidence.…
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.