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-refactorgit 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-refactor)<a href="https://agentmods.dev/skills/bravew/trove/trove-refactor"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-refactor/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-refactor"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-refactor.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.00062 | $0.00500 |
| Opus 5.5 | $0.00025 | $0.00200 |
| Sonnet 5.5 | $0.00012 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
trove-refactor 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-refactor
A refactor changes structure while holding behavior constant. The discipline is proving that "constant" is true.
Workflow
- Pin the behavior. Characterization test or snapshot of current behavior first. A type-check and a lint passing are not a behavior pin — they don't catch a changed result.
- Name the target shape. What the structure should be after (use
trove-architectfor non-trivial reshapes). - Subtract before adding. Remove dead weight and duplication first, then build on the simpler base.
- Small behavior-preserving steps. Migrate callers and delete the legacy API in the same wave (
trove-principle-migrate-then-delete); don't leave a compatibility shim. - Prove it unchanged. Re-run the pinned behavior against the real artifact — same inputs, same outputs.
trove-verify. - Confirm reader load dropped. If the change didn't make the code easier to trace, question whether it earned its place.
Anti-patterns
- Smuggling behavior change into a refactor. If behavior must change, that's a separate, named change with its own test — split it out.
- Calling a green type-check "proof". Behavior parity needs a behavioral check, not a compile.
- Leaving the old API alive "just in case." That's two ways to do one thing; delete it in the same wave.
For a large or cross-cutting refactor (a migration across many call sites), treat each component as its own small step with its own behavior pin.
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 · 34 lines · 62 tokens per session scan A ba4896a7ff53
trove-refactor is a skill published in the GitHub repository bravew/trove (10 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 500 once invoked, about $0.0002 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
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart. Do not use for ordinary review, style feedback, or general improvement suggestions.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.