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 commands/bravew/trove/prgit 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.00006 | $0.00606 |
| Opus 5 | $0.00003 | $0.00303 |
| Sonnet 5 | $0.00001 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
pr 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 3d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
PR Title (if provided): $ARGUMENTS
Process
-
Detect base branch and verify state
git branch --show-current git status # Fetch known integration branches git fetch origin --no-tags 2>/dev/null BASE=staging best_distance="" for candidate in staging production main master develop; do mb=$(git merge-base HEAD "origin/$candidate" 2>/dev/null) || continue distance=$(git rev-list --count "$mb"..HEAD 2>/dev/null) || continue if [[ -z "$best_distance" ]] || [[ "$distance" -lt "$best_distance" ]]; then best_distance=$distance BASE=$candidate fi done echo "Detected base branch: $BASE" -
Review changes
git diff $BASE...HEAD --stat git log $BASE..HEAD --oneline -
Ensure commits are ready
- Stage any uncommitted changes if needed
- Create atomic commits with conventional commit messages
-
Run validation using project-appropriate tools:
Stack Commands Python ruff check . && ruff format --check . && pytest -vNode/React/Vue pnpm lint && pnpm type-check && pnpm test:run && pnpm buildNext.js npm run lint && npm run type-check && npm run buildSwift swift build && swift test -
Push to remote
git push -u origin HEAD -
Create PR targeting the detected base branch
gh pr create --base "$BASE" --title "<title>" --body "$(cat <<'EOF' ## Summary [Brief description of what this PR does] ## Changes - [List key changes with file references] ## Testing **Automated:** - [ ] Lint/format passes - [ ] Type checking passes - [ ] Tests pass - [ ] Build succeeds **Manual:** - [ ] [Specific flow tested] - [ ] Manual testing completed ## Breaking Changes [List any breaking changes or "None"] ## Checklist - [ ] Code follows project conventions - [ ] Self-reviewed - [ ] Tests added/updated EOF )"
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.
- 3d ago First seen · 97 lines · 6 tokens per session scan A e4974ec6dfba
pr is a command published in the GitHub repository bravew/trove (10 stars, last pushed 4d ago), licensed MIT. It adds 6 tokens to every session and 606 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.