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 skills/anishfyi/trove/initnpx skills add anishfyi/trove --skill initgit clone --depth 1 https://github.com/anishfyi/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/anishfyi/trove/init)<a href="https://agentmods.dev/skills/anishfyi/trove/init"><img src="https://agentmods.dev/badge/skills/anishfyi/trove/init.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 | $0.00089 | $0.00866 |
| Opus 5 | $0.00044 | $0.00433 |
| Sonnet 5 | $0.00018 | $0.00173 |
| Haiku 4.5 | $0.00009 | $0.00087 |
Grade A, and why
init 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize a Trove
A Trove is a personal, file-based knowledge index that grows as you use Claude Code. It is just plain files on disk (Markdown for prose, JSON for structured data), so it is portable, greppable, diffable, and yours. This skill creates it.
Steps
-
Pick a scope (if the user did not say in the argument):
- User scope
~/.claude/trove/(default): one trove that follows you across every project. - Project scope
./.claude/trove/: a trove that lives in and travels with this repository (commit it to share with a team).
If unclear, default to user scope and mention you did.
- User scope
-
Scaffold the structure. Create the directory, an
entries/subfolder, and anINDEX.md:TROVE="$HOME/.claude/trove" # or "$PWD/.claude/trove" for project scope mkdir -p "$TROVE/entries"Then write
INDEX.md(only if it does not already exist) with this exact starter:# Trove Index > Your personal Claude Code trove. One line per entry, newest first. > Loaded into context at the start of every session by the trove plugin. > Capture new entries with /trove:remember and search with /trove:recall. <!-- entries below --> -
Confirm to the user with the resolved path and the three commands they will use:
/trove:rememberto capture,/trove:recallto search, and that it auto-loads each session.
The entry format (so every skill agrees)
Each fact is its own file in entries/, in one of two formats. The remember skill chooses by
the shape of the content: Markdown for prose, JSON for structured data.
Markdown entries/<slug>.md for prose: decisions, gotchas, conventions, narrative notes.
---
title: <Human readable title>
slug: <kebab-case-slug>
type: decision | gotcha | preference | reference | project | snippet
created: <YYYY-MM-DD>
tags: [tag1, tag2]
---
<One or two short paragraphs: the durable thing worth keeping.>
**Why it matters:** <when this applies / why future-you will care>
**Related:** [[other-slug]]
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 · 91 lines · 89 tokens per session scan A 5678e6c5f707
init is a skill published in the GitHub repository anishfyi/trove (1 stars, last pushed 8d ago), licensed MIT. It adds 89 tokens to every session and 866 once invoked, about $0.0004 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 skills, from other repositories
setup
Scaffold a complete knowledge system. Detects platform, conducts conversation, derives configuration, generates everything. Validates against 15 kernel primitives. Triggers on "/setup", "/setup --advanced", "set up my knowledge system", "create my vault".
rethink
Challenge system assumptions against accumulated evidence. Triages observations and tensions, detects patterns, generates proposals. The scientific method applied to knowledge systems. Triggers on "/rethink", "review observations", "challenge assumptions", "what have I learned".
architect
Research-backed evolution advice for your knowledge system. Analyzes health reports, friction patterns, and derivation history to propose specific changes with research justification. Never auto-implements — proposals require your approval.
health
Run condition-based vault health diagnostics. 8 categories — schema compliance, orphan detection, link health, description quality, three-space boundaries, processing throughput, stale notes, MOC coherence. 3 modes — quick (schema+orphans+links), full (all 8), three-space (boundary violations only). Returns actionable…
graph
Interactive knowledge graph analysis. Routes natural language questions to graph scripts, interprets results in domain vocabulary, and suggests concrete actions. Triggers on "/graph", "/graph health", "/graph triangles", "find synthesis opportunities", "graph analysis".
refactor
Plan vault restructuring from config changes. Compares config.yaml against derivation.md, identifies dimension shifts, shows restructuring plan, executes on approval. Triggers on "/refactor", "restructure vault".