Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bravew/trovenpx agentmods add skills/bravew/trove/trove-shipWrote 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/bravew/trove/trove-ship)<a href="https://agentmods.dev/skills/bravew/trove/trove-ship"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-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/bravew/trove/trove-ship"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-ship.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.00045 | $0.01059 |
| Opus 5.5 | $0.00018 | $0.00424 |
| Sonnet 5.5 | $0.00009 | $0.00212 |
| Haiku 4.5 | $0.00005 | $0.00106 |
Grade A, and why
trove-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 1mo 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
If a sibling skill in this plugin matches the request more directly, defer to it. See AGENTS.md (or docs/routing.md in the marketplace) for the per-plugin routing index.
You are an orchestrator: when a step maps to another skill (e.g., review, security-review, design-review), call out the delegation explicitly rather than re-implementing it inline.
trove-ship — Pre-Land Preparation
trove-ship is an orchestrator, not a leaf skill. It walks a diff
through review → commit → ship-readiness check and stops at a final
Decision Gate before anything destructive (push, PR, tag).
The repo's
release.ymlworkflow handles the actual version bump and tag.trove-shipprepares the diff up to "ready to push"; the user (or CI on merge) handles publish.
Inputs
- A working tree with uncommitted or branch-local changes.
- Optional: target base branch, scope of the change (feature / fix / chore).
Workflow
Stage 1 — Review the diff
Hand off to trove-review. Walk the diff through the standard checklist
(correctness, security, performance, maintainability, testing). If the
diff touches sensitive surfaces (auth, payments, secrets), also delegate
to trove-security-review for a second pass — this is in trove-review's
benefits-from for exactly this reason.
Optional: dispatch a read-only sub-agent to verify a specific concern the review surfaced (e.g., "is this the only callsite of the legacy function?"). See docs/orchestration.md for delegation phrasing.
Stage 2 — Author the commit
Hand off to trove-commit. Generate the conventional-commit message
from the diff. Don't substitute your own format — trove-commit owns the
conventions (type, scope, body, footer).
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.
- 1mo ago First seen · 105 lines · 45 tokens per session scan A 3bb75a9e737b
trove-ship is a skill published in the GitHub repository bravew/trove (10 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,059 once invoked, about $0.0002 per session on Opus 5.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-11.
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 8. 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 automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
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…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.