Companion is a self-hosted, multi-tenant hub for managing personal and organizational SKILL.md libraries used by coding agents. It is for organizations that need to store, validate, version, share, install, update, and synchronize agent skills, with optional named companions that have persistent workspaces and chats. The catalogue skills, agents, and instructions are resources managed or used within this workflow.
Borrowing it
Nothing to install: this file belongs to The-Vibe-Company/companion. 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/The-Vibe-Company/companion/main/.agents/skills/ship-pr-dev/SKILL.mdgit clone --depth 1 https://github.com/The-Vibe-Company/companionWrote 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/the-vibe-company/companion/ship-pr-dev)<a href="https://agentmods.dev/skills/the-vibe-company/companion/ship-pr-dev"><img src="https://agentmods.dev/badge/skills/the-vibe-company/companion/ship-pr-dev/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/the-vibe-company/companion/ship-pr-dev"><img src="https://agentmods.dev/badge/skills/the-vibe-company/companion/ship-pr-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00134 | $0.02227 |
| Opus 5 | $0.00067 | $0.01113 |
| Sonnet 5 | $0.00027 | $0.00445 |
| Haiku 4.5 | $0.00013 | $0.00223 |
Grade A, and why
ship-pr-dev 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 9d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship PR
Own delivery from the current branch to a PR that is ready for human review. The coordinator keeps scope, architecture, safety decisions, Git state, PR state, and final verification. Delegate only bounded work orders whose saved context is worth more than the dispatch overhead.
Protected Invariants
- Never merge, enable auto-merge, force-push, hard-reset, discard user work, or rewrite public history unless the user explicitly requests that exact operation.
- Stage only intentional files. Never use broad staging when unrelated changes exist.
- The coordinator is the only Git owner. Workers never stage, commit, push, rebase, merge, stash, create/update a PR, or alter CI settings.
- Allow at most one write-capable worker at a time. Reviewers and investigators are read-only.
review-code-devis the single independent review gate. Do not run a separate Ship PR review board or a second full frontend review; pass the required risk and frontend lenses into one review run.- A PR is ready only when local verification is fresh,
review-code-devhas no unresolved P0/P1 findings, every visible non-skipped CI item is green on the latest pushed SHA, and the report-onlycapture-learning-toolspass completed. - Never bypass checks, use
--no-verify, weaken validation, or claim success while CI is pending, stale, partially inspected, failed, cancelled, or attached to another SHA. - Never expose secrets. Stop push/PR work, redact values, and give rotation guidance if one is found.
- Write artifacts only under ignored
plans/ship-pr-dev/runs/<timestamp>-<repo-slug>/.
References
Read only what the current phase needs:
references/workflow.md— detailed delivery loop and retry policy.references/agent-routing.md— host-specific worker models, effort, context, budgets, telemetry, and fallbacks.references/readiness-gates.md— hard blocks and required evidence.references/pr-template.md— PR body and final handoff.
Load the installed review-code-dev skill before the review gate and capture-learning-tools only for the final report-only learning pass. Resolve skills by canonical name; never guess an install path.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- companion.json 4.1 KB
- evals/evals.json 6.9 KB
- references/agent-routing.md 5.5 KB
- references/pr-template.md 1.9 KB
- references/readiness-gates.md 3.6 KB
- references/workflow.md 3.8 KB
- scripts/.gitignore 23 B
- scripts/collect_ship_context.py 7.3 KB runs code
- scripts/prepare_ship_run.py 3.0 KB runs code
- scripts/test_collect_ship_context.py 2.3 KB runs code
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.
- 9d ago First seen · 144 lines · 134 tokens per session scan A c967308f5d6c
ship-pr-dev is a skill published in the GitHub repository The-Vibe-Company/companion (2,401 stars, last pushed 3d ago), licensed MIT. It adds 134 tokens to every session and 2,227 once invoked, about $0.0007 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-09-02.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage repo-sync on macOS for shared documents and team context. Use when asked what repo-sync does, to automatically sync a repo, add a repo to repo-sync, stop syncing or un-sync a repo, check sync health, configure repo-sync, uninstall it, or install and maintain its bundled agent skill. Ordinary one-time Git pulls…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.