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.
git clone --depth 1 https://github.com/slavins-co/cellartracker-mcpWrote 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/plugins/slavins-co/cellartracker-mcp/cellartracker-mcp)<a href="https://agentmods.dev/plugins/slavins-co/cellartracker-mcp/cellartracker-mcp"><img src="https://agentmods.dev/badge/plugins/slavins-co/cellartracker-mcp/cellartracker-mcp/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/plugins/slavins-co/cellartracker-mcp/cellartracker-mcp"><img src="https://agentmods.dev/badge/plugins/slavins-co/cellartracker-mcp/cellartracker-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cellartracker-mcp 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 8d 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
{
"name": "cellartracker-mcp",
"description": "CellarTracker wine cellar management — MCP tools for inventory, drinking recommendations, purchase history, and wishlist. Includes skills for data interpretation and purchase evaluation.",
"version": "0.5.0",
"author": {
"name": "Brad Slavin"
},
"license": "MIT"
}
What it installs
The manifest is a name and a version. 2 skills, 2 MCP servers travel with it, and installing the plugin installs all of them — 270 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 10 lines scan A d97289e2f9ab
cellartracker-mcp is a plugin published in the GitHub repository slavins-co/cellartracker-mcp (6 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
sprint
Orchestrate staged milestones with native subagents on Claude Code or Oh My Pi, plus codex or mimo executors on Claude Code.
ui-clone-skills
Motion forensics for the animated web. Four jobs against a live URL: decode (analyse motion + build, no code), clone (URL → React + Tailwind), verify (AE/SSIM + motion-parity score vs. an existing impl), extract (raw JSON dump). Extracts real CSS and animation params (GSAP / Framer Motion / Lenis / anime.js) directly…
neatcontext marketplace
Save Claude Code work as reusable, domain-aware context.
neatcontext
Save Claude Code work as reusable, domain-aware context.
code-cleanup
Evidence-first cleanup of agent trajectory residue, dead islands, split-brain authority, stale dependencies, and unnecessary code across repositories.
backend-architecture
Small, opinionated architecture guide for production backend services across languages and frameworks.