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 agentmods add skills/bravew/trove/trove-commitnpx skills add bravew/trove --skill trove-commitgit clone --depth 1 https://github.com/bravew/troveWhat 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 | $0.00026 | $0.00619 |
| Opus 5 | $0.00013 | $0.00309 |
| Sonnet 5 | $0.00005 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
trove-commit 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 2d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trove · v2026.7.4
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
Commit Message Conventions
Format
<type>(<scope>): <subject>
<body>
<footer>
Types
| Type | When to Use |
|---|---|
feat |
New feature |
fix |
Bug fix |
refactor |
Code restructuring (no behavior change) |
docs |
Documentation only |
test |
Adding or updating tests |
chore |
Build, deps, config changes |
perf |
Performance improvement |
style |
Code style (formatting, semicolons) |
ci |
CI/CD configuration |
Rules
- Subject line: imperative mood, lowercase, no period, max 72 chars
- Body: explain WHY, not WHAT (the diff shows what changed)
- Scope: optional, identifies the module/area (e.g.,
auth,api,ui) - Breaking changes: add
BREAKING CHANGE:in footer
Stacking and prose
Commit liberally and treat each commit as a future PR: prefer several small, ordered, independently reviewable commits over one fat commit. Rebase them into a clean sequence before opening the PR. Run the message body through trove-unslop (its benefits-from) so it reads as plain prose — explain the why, drop boilerplate.
Direct Commit Workflow
When invoked as an action, create a commit only for a single logical change.
- Inspect
git status --short, recent commits, and the relevant diff. - If paths are provided, limit the review and staging to those paths.
- Stage specific files with
git add <paths>; avoidgit add -Aunless the whole working tree is clearly one change. - Create the commit with the conventional subject and a body when the why is not obvious.
- Report the commit hash, message, and files committed.
If the working tree mixes unrelated changes, stop and name the smaller commit slices. Never include AI-generated or co-author boilerplate.
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.
- 2d ago First seen · 80 lines · 26 tokens per session scan A c5e9be019524
trove-commit is a skill published in the GitHub repository bravew/trove (10 stars, last pushed 3d ago), licensed MIT. It adds 26 tokens to every session and 619 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…