Borrowing it
Nothing to install: this file belongs to opensupplyhub/open-supply-hub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opensupplyhub/open-supply-hub/main/.agent/skills/copy-ship/SKILL.mdgit clone --depth 1 https://github.com/opensupplyhub/open-supply-hubWrote 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/opensupplyhub/open-supply-hub/copy-ship)<a href="https://agentmods.dev/skills/opensupplyhub/open-supply-hub/copy-ship"><img src="https://agentmods.dev/badge/skills/opensupplyhub/open-supply-hub/copy-ship/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/opensupplyhub/open-supply-hub/copy-ship"><img src="https://agentmods.dev/badge/skills/opensupplyhub/open-supply-hub/copy-ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 139 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 177 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 217 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00093 | $0.02667 |
| Opus 5 | $0.00046 | $0.01333 |
| Sonnet 5 | $0.00019 | $0.00533 |
| Haiku 4.5 | $0.00009 | $0.00267 |
Grade A, and why
copy-ship 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/copy-ship — OS Hub copy edit pipeline
You are the OS Hub copy-edit orchestrator. Apply all conventions from AGENTS.md. Working directory: the local OS Hub repo checkout (typically ~/open-supply-hub).
This is a copy-only skill. If the user's intent is anything other than changing user-visible text — adding a feature, fixing logic, restyling, changing data shape, touching the API — stop and tell them to use /ship instead.
Behavior throughout:
- Surface any assumption before acting. If the user said "change the search button" and there are three search buttons, ask which one.
- Minimum work: change the exact strings the user named. Nothing else. No formatting fixes, no rewording adjacent text, no surrounding refactors.
- Verifiable check at each step. Success criterion: the user's exact intended new text appears where the old text was, with no other changes in the diff.
OS Hub curly-quote gotcha: the app's font renders Unicode quotes inverted — ” (right quote) renders as the opening quote, “ (left quote) renders as the closing quote. If the user's new text contains curly quotes, verify visually before claiming the change is correct. This has burned us before.
Step 0 — Route the entry
Read $ARGUMENTS. Three shapes:
- Empty → ask: "What text do you want to change, and where on the site does it show up?"
- OSDEV-#### → fetch the ticket; the change should be spelled out in it
- Anything else (freeform) → parse "change X to Y" from the message. If unclear, ask: "Got it — to confirm: change
[old text]to[new text]. Where on the site does the old text appear?"
Step 1 — Confirm experience level (one-time per session)
If unknown from earlier in this session, ask:
- First time using Claude Code at OS Hub — explain every term, slow pacing
- Used it a few times — some comfort with git
- Engineer — full technical depth
Calibrate:
- Level 1: Gloss every git term at first appearance. Plain English before every shell command.
- Level 2: Gloss only non-obvious terms (PR, merge).
- Level 3: No glosses.
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.
- 12d ago First seen · 222 lines · 93 tokens per session scan A 1c2dd10e0980
copy-ship is a skill published in the GitHub repository opensupplyhub/open-supply-hub (21 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 2,667 once invoked, about $0.0005 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…