plugin
Open on GitHub
mine — Claude Code plugin: session database with queries
Writes every Claude session into a local SQLite file and answers questions about cost, tokens and past conversations.
Install into Claude Code · Plugin marketplace
All methods and platforms ↓
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mine@claude-communityWhat mine does
Hooks feed each session into SQLite as you work. The /mine skill then takes a plain-language question about spend, token counts, tools, projects, errors or cache hits and looks across everything you have run.
Error memory is built in: repeat a mistake and the plugin warns you. It also flags cost anomalies and weighs API value against a subscription. Scope the answer to one project or keep it global.
It relies on stock Python, so nothing else needs installing. The database sits on your machine and stays there after the plugin is gone, which matters on a small disk.
What it helps with
- check token usage for one project
- find the session where a file came up
- get warned about a mistake you keep making
- compare API spend against a subscription
- see how well the cache is doing
Example prompts for the agent
- How much did this project cost me this week?
- Find every session where I edited
auth.ts. - Which mistakes do I repeat most?
How to install mine
Plugin marketplace
/plugin marketplace add anthropics/claude-plugins-community/plugin install mine@claude-communityStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about mine
How do I install mine in Claude Code?
Add the marketplace with /plugin marketplace add anthropics/claude-plugins-community, then run /plugin install mine@claude-community.
What does mine do?
It stores your Claude sessions in a local SQLite database and exposes a /mine skill that answers natural-language questions about cost, tokens, tools and earlier chats.
Does it need extra dependencies?
No. The plugin runs on the Python standard library alone, with no external packages.
Source text
mine · MIT
# agent tips a personal handbook for using agents to build things and handle everyday work. the site brings together everyday work, building for fun or serious use, and personal infrastructure. product guides provide the specific controls. [read the handbook](https://agents.anipotts.com) or go directly to a principal guide: <!-- generated:guides:start --> - [codex](https://agents.anipotts.com/guides/codex/) - [claude code](https://agents.anipotts.com/guides/claude-code/) - [grok](https://agents.anipotts.com/guides/grok/) - [start here](https://agents.anipotts.com/handbook/operating-agents/) - [choosing an agent setup](https://agents.anipotts.com/handbook/choosing-a-setup/) - [everyday work](https://agents.anipotts.com/handbook/everyday-work/) - [building things](https://agents.anipotts.com/handbook/building-things/) - [personal infrastructure](https://agents.anipotts.com/handbook/personal-infrastructure/) - [backups and getting your work back](https://agents.anipotts.com/handbook/backups-and-recovery/) - [how coding agents got here](https://agents.anipotts.com/handbook/history/) - [where this comes from](https://agents.anipotts.com/handbook/method-and-sources/) <!-- generated:guides:end --> ## resume here The [reassessment](editorial/reassessment.md) records a disposition for all 24 pages present at the start. Four shared pages now have a publishable first edition. The [section audit](editorial/reassessment-details.md) covers headings, copy, source conflicts, and both recovered stashes. The [review ledger](editorial/review-ledger.md) owns wording acceptance and the local `/__progress/` page derives the current review map. - [ ] review the homepage bridge and remaining start page copy - [ ] review deeper backup page copy in small batches, continuing with “choose one backup workflow” - [ ] reassess the published everyday work and building copy in small wording batches - [ ] review corrected product copy in small wording batches The October 17 [accuracy disposition](editorial/reassessment-details.md#accuracy-corrections-october-17-2026) records the product corrections and the limits of the source and example checks. Exact wording acceptance remains in the review ledger. [PR #329](https://github.com/anipotts/agents/pull/329) carries these corrections and their final check and release evidence. [PR #327](https://github.com/anipotts/agents/pull/327) carries the organized publication and backup first edition. Its exact-head checks and deployment records own release evidence. [PR #326](https://github.com/anipotts/agents/pull/326) carries the setup, reconciled design work, audit, and accepted opening copy through protected checks. Its check and deployment records own release evidence. The structure is accepted with separate building paths for curiosity and work with business or real world consequences. The homepage headline/subtitle, everyday first-task example and exact planning tradeoff paragraph are accepted; the infrastructure opening and six sections also have exact acceptance records. The deeper backup outline is accepted; its body copy remains under review. Ani authorized organized publication of the shared pages on October 12. Publication authority does not extend exact wording acceptance to newly added prose. Archived plugins retain compatibility through November 5, 2026. ## project layout `content/` owns guide copy; `editorial/` owns sources and review evidence; `src/` renders the site; `scripts/` owns checks. `design.md` owns visual rules. [Worktree setup](docs/worktrees.md) describes reusable setup and preview actions. The handbook review stays in the saved local `main` checkout. ## evidence principle <!-- generated:evidence:start --> - `tested`: reproduced in a named environment and version, with the tester and limits stated - `official source`: confirmed in current primary documentation or source code - `analysis`: a judgment derived from stated evidence - `open question`: current evidence is missing or incomplete <!-- generated:evidence:end --> citations sit beside the claims they support. tested observations name their limits, while source based claims stay distinct from personal analysis. ## local verification ```bash node scripts/project.mjs setup node scripts/project.mjs verify ``` built and maintained by [ani potts](https://anipotts.com). corrections with primary sources or reproducible field evidence are welcome. MIT
© anipottsbuilds · MIT · anipottsbuilds/agents
Similar plugins
All plugins for Agent setup: memory, context, orchestration →
ponytail ponytail steers Claude Code toward small, direct solutions and away from abstractions nobody asked for. Use it when you want the agent to build on what the project already has.
★ 176,443repo stars
impeccable Hands your agent a designer's vocabulary: 24 commands like polish, audit and bolder, so UI feedback stops being “make it pretty”.
★ 88,212repo stars
last-30-days-skill Searches the web for what people posted about a topic in the last month and turns it into one structured brief.
★ 65,508repo stars
claude-hud Shows context usage, rate limits, running tools and todo progress under your input line. Useful when a session runs long and you want to watch the spend.
★ 28,841repo stars
understand-anything Turns codebases or markdown wikis into an interactive knowledge graph with a browser dashboard. Helps navigate unfamiliar repositories without reading files blindly.
★ 88,314repo stars
mem0 Adds persistent memory to Claude Code so your agent retains project context across terminal sessions.
★ 67,829repo stars
