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/bvdr/claude-pluginsWrote 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/commands/bvdr/claude-plugins/umami-track)<a href="https://agentmods.dev/commands/bvdr/claude-plugins/umami-track"><img src="https://agentmods.dev/badge/commands/bvdr/claude-plugins/umami-track/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/commands/bvdr/claude-plugins/umami-track"><img src="https://agentmods.dev/badge/commands/bvdr/claude-plugins/umami-track.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.00032 | $0.02054 |
| Opus 5.5 | $0.00013 | $0.00822 |
| Sonnet 5.5 | $0.00006 | $0.00411 |
| Haiku 4.5 | $0.00003 | $0.00205 |
Grade A, and why
umami-track 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.
How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Umami Tracking Implementation
Implement comprehensive tracking in a user's codebase. Two modes: analyze and suggest a tracking plan, or directly implement specific tracking.
Prerequisites
Read .umami.json from project root for host, websiteId, domain. If missing, invoke bvdr:umami-setup first.
Mode A: Tracking Plan
Triggered by: "help me track", "what should I track", "analyze my app", "tracking plan"
Step 1: Scan the codebase
Look for:
- Page routes/views — Next.js
app/orpages/directory, React Router routes, plain HTML files - User interaction points — forms, buttons with onClick/onSubmit, CTAs, checkout flows
- Auth flows — login, signup, logout, registration pages/components (candidates for
umami.identify()) - Revenue/purchase events — cart, checkout, payment, subscription components
- Existing Umami tracking — search for
umami.track,umami.identify,data-umami-eventalready in code
Step 2: Present tracking plan
Organize by category:
Pageviews:
- List auto-tracked pages (Umami tracks all pageviews by default when
data-auto-trackis not"false") - Flag any pages that need manual tracking (SPAs with client-side routing that Umami might miss)
Identity (umami.identify):
- Where to call
umami.identify(userId, { ... })— typically after login/signup - What session properties to attach (name, email, plan, role, etc.)
- Distinct ID enables cross-session and cross-device tracking
Core Events:
- Signup completed, login, logout
- Key feature first-use
- Onboarding steps
Conversion Events:
- Form submissions
- Purchase/checkout completion
- Subscription actions
- CTA clicks
Engagement Events:
- Feature discovery clicks
- Navigation patterns
- Search usage
- Filter/sort interactions
Revenue Events:
- Must include both
revenue(number) andcurrency(ISO 4217 string) - Example:
{ revenue: 49.99, currency: 'USD' }
Step 3: After approval, implement
Implement each tracking point using the appropriate method (see Mode B).
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 · 284 lines · 32 tokens per session scan A 7253f9437c21
umami-track is a command published in the GitHub repository bvdr/claude-plugins (4 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 2,054 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-08-31.
Other commands, from other repositories
dead-code-scan
Scan for dead code, unused imports, duplicates, and zombie code across the project.
esp-teach
One-time project setup -- discover hardware, find datasheets, persist context to CLAUDE.md.
swift-critique
Critique SwiftUI code for patterns, design, clean code, accessibility, and performance.
dotnet-harden
Scan and harden .NET backend code against high-impact anti-patterns such as sync-over-async, lifetime bugs, fat endpoints, and fragile SignalR state.
rust-critique
Deep code critique — read the target Rust code and apply the full review process. Evaluates soundness, ownership, error handling, type design, async correctness, performance, and architecture. Think like a senior Rust engineer giving honest feedback.
rust-harden
Harden Rust code — replace unwrap with proper error handling, add safety comments to unsafe blocks, enable overflow checks, validate inputs at boundaries. The defensive hardening pass.