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-worktreegit 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-worktree)<a href="https://agentmods.dev/skills/bravew/trove/trove-worktree"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-worktree/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-worktree"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-worktree.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.00028 | $0.00421 |
| Opus 5.5 | $0.00011 | $0.00168 |
| Sonnet 5.5 | $0.00006 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
trove-worktree 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
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
If a sibling skill in this plugin matches the request more directly, defer to it. See AGENTS.md (or docs/routing.md in the marketplace) for the per-plugin routing index.
trove-worktree
Spike or risky work goes in a worktree, never on the user's branch.
Workflow
- Check the current branch and worktree status.
- Propose a worktree path and branch name.
- Create the worktree before edits when the user approves or when the request already asked for a spike.
- Keep generated or experimental churn inside the worktree.
- When done, summarize what to keep and what to discard.
Decision Gate: worktree needed
Context: Experiments can dirty unrelated files or block the user's branch. Question: Should this work happen in a separate git worktree? Options:
- A. Yes - create the worktree first.
- B. No - continue in the current checkout.
- C. Ask the user because the branch state is unclear. Default: A for spikes and risky cross-system refactors.
Cleanup
Do not remove a worktree without explicit confirmation. Preserve user changes.
Branch Naming
For a branch-only request, generate a local branch name from the user's request:
feat/, fix/, chore/, docs/, refactor/, test/, or perf/ plus a
short kebab-case description. Check whether it already exists and append
-v2, -v3, and so on until unique. Create it locally only; push later through
the ship workflow.
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 · 28 tokens per session scan A 44c6acadf8b1
trove-worktree is a skill published in the GitHub repository bravew/trove (10 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 421 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-09-11.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…