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 commands/bvdr/claude-plugins/umami-setupgit clone --depth 1 https://github.com/bvdr/claude-pluginsWhat 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.00029 | $0.01207 |
| Opus 5 | $0.00015 | $0.00603 |
| Sonnet 5 | $0.00006 | $0.00241 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
umami-setup scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "{host}/api/auth/login" \ How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Umami Setup
Configure a project to use Umami Analytics. Handles authentication, website selection, script tag installation, and connection verification.
Flow
-
Check if
.umami.jsonexists at project root- If exists → offer re-run options (see below)
- If not → proceed with setup
-
Collect connection details using AskUserQuestion:
- Umami host URL (e.g.,
https://analytics.mysite.com) - Username
- Password
- Umami host URL (e.g.,
-
Authenticate against the Umami instance:
curl -s -X POST "{host}/api/auth/login" \
-H "Content-Type: application/json" \
-d '{"username": "{username}", "password": "{password}"}'
Response: { "token": "eyT...", "user": { "id": "...", "username": "...", "role": "...", "isAdmin": true } }
If authentication fails, show the error and ask the user to check their credentials.
- List available websites:
curl -s "{host}/api/websites" \
-H "Authorization: Bearer {token}"
Present the list to the user and let them pick one. If they want to create a new website, confirm first then:
curl -s -X POST "{host}/api/websites" \
-H "Authorization: Bearer {token}" \
-H "Content-Type: application/json" \
-d '{"name": "{name}", "domain": "{domain}"}'
- Write
.umami.jsonto project root:
{
"host": "https://analytics.mysite.com",
"websiteId": "94db1cb1-74f4-4a40-ad6c-962362670409",
"token": "eyTxxxxx...",
"domain": "mysite.com"
}
-
Add
.umami.jsonto.gitignore:- If
.gitignoredoesn't exist → create it with.umami.json - If
.gitignoreexists but doesn't contain.umami.json→ append it - If already listed → skip
- If
-
Detect project framework and install the tracker script tag:
Next.js (app router): Add to
app/layout.tsxorapp/layout.js:import Script from 'next/script' // Inside the <body> tag: <Script src="{host}/umami.js" data-website-id="{websiteId}" strategy="afterInteractive" />Next.js (pages router): Add to
pages/_app.tsxorpages/_document.tsx:import Script from 'next/script' <Script src="{host}/umami.js" data-website-id="{websiteId}" strategy="afterInteractive" />
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.
- 2d ago First seen · 153 lines · 29 tokens per session scan A 6247fac539be
umami-setup is a command published in the GitHub repository bvdr/claude-plugins (3 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,207 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
dead-code-clean
Actively find and remove dead code, unused imports, duplicates, and zombie code.
swift-critique
Critique SwiftUI code for patterns, design, clean code, accessibility, and performance.
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.