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 bravew/trove --skill trove-commitgit clone --depth 1 https://github.com/bravew/troveWrote 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-commit)<a href="https://agentmods.dev/skills/bravew/trove/trove-commit"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-commit/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-commit"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-commit.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.00026 | $0.00607 |
| Opus 5.5 | $0.00010 | $0.00243 |
| Sonnet 5.5 | $0.00005 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00061 |
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 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 — 78 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.
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.
- 1mo ago Changed · -2 lines 04127d204a97
- 1mo 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 yesterday), licensed MIT. It adds 26 tokens to every session and 607 once invoked, about $0.0001 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-08-31.
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.