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/new-branchgit 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/new-branch)<a href="https://agentmods.dev/commands/bravew/trove/new-branch"><img src="https://agentmods.dev/badge/commands/bravew/trove/new-branch.svg" alt="Measured on agentmods" 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.00479 |
| Opus 5 | $0.00004 | $0.00239 |
| Sonnet 5 | $0.00002 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
new-branch 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 6d 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 Branch
Generate a conventional branch name based on user request and create a new git branch.
Variables
User request: $ARGUMENTS
Instructions
Step 1: Check Current Branch
- Check current branch:
git branch --show-current - Warn (but proceed) if not on a standard base branch (staging, production, main, master, develop)
Step 2: Generate Branch Name
Prefixes:
feat/- New feature or enhancementfix/- Bug fixchore/- Maintenance tasks (dependencies, configs, etc.)docs/- Documentation only changesrefactor/- Code refactoring (no functionality change)test/- Adding or updating testsperf/- Performance improvements
Naming Rules:
- Use kebab-case (lowercase with hyphens)
- Be descriptive but concise (max 50 characters)
- No special characters except hyphens, no spaces
Examples:
- "Add user settings page" →
feat/add-user-settings - "Fix SSE stream disconnect" →
fix/sse-stream-disconnect - "Update README documentation" →
docs/update-readme - "Refactor state management" →
refactor/state-management
Step 3: Check Branch Exists
If the branch name already exists, append -v2, -v3, etc. until unique:
if git show-ref --verify --quiet refs/heads/<branch-name>; then
COUNTER=2
while git show-ref --verify --quiet refs/heads/<branch-name>-v$COUNTER; do
COUNTER=$((COUNTER + 1))
done
BRANCH_NAME="<branch-name>-v$COUNTER"
fi
Step 4: Create and Checkout Branch
git checkout -b <branch-name>
git branch --show-current
Important: Branch is created locally only — push happens later via the pr or ship command.
Report
Output the branch name and confirm checkout.
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.
- 6d ago First seen · 73 lines · 8 tokens per session scan A cdc31f6d2c0f
new-branch is a command published in the GitHub repository bravew/trove (10 stars, last pushed 7d ago), licensed MIT. It adds 8 tokens to every session and 479 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
commit
智能生成 Git 提交信息并提交.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
Command "release-plan" from alisunstar/OpenSunstar, covering /rd:release-plan — 发布计划, 先读, 执行, 产物 and 人工确认.