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.
git 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/commands/bravew/trove/commit)<a href="https://agentmods.dev/commands/bravew/trove/commit"><img src="https://agentmods.dev/badge/commands/bravew/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/commands/bravew/trove/commit"><img src="https://agentmods.dev/badge/commands/bravew/trove/commit.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.00008 | $0.00322 |
| Opus 5.5 | $0.00003 | $0.00129 |
| Sonnet 5.5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
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.
What it actually says
Create Git Commit
Context
- Current status: !
git status --short - Recent commits: !
git log --oneline -5
Task
Create an atomic git commit for the uncommitted changes, or for these specific files if provided:
$ARGUMENTS
Commit Message Format: <type>(<scope>): <description>
- Types:
feat,fix,docs,style,refactor,test,chore,perf - Scope (optional): derive from the primary area/module affected by the change
- Present tense, imperative mood
- 72 chars or less for subject (aim for 50)
- Lowercase, no period at end
Rules:
- One logical change per commit
- Prefer staging specific files over
git add -A - NEVER mention Claude Code, Anthropic, co-authored by, or AI-generated
Steps
- Review changes with
git diff HEAD - Determine type and scope from the changed files
- Stage relevant files with
git add <files> - Create commit with
git commit -m "<type>(<scope>): <description>"
Report
End with explicit status:
- DONE: Commit hash, message, files committed
- BLOCKED: Why commit failed, what was attempted, recommendation
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 · 47 lines · 8 tokens per session scan A c235948fcb8b
commit is a command published in the GitHub repository bravew/trove (10 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 322 once invoked, about $0.0000 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 commands, from other repositories
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Context-aware Git commit assistant with smart pre-commit checks.