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/mthines/agent-skills/rum-trackingnpx skills add mthines/agent-skills --skill rum-trackinggit clone --depth 1 https://github.com/mthines/agent-skillsWrote 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/mthines/agent-skills/rum-tracking)<a href="https://agentmods.dev/skills/mthines/agent-skills/rum-tracking"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/rum-tracking.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.1 | $0.00187 | $0.02441 |
| Opus 5 | $0.00093 | $0.01221 |
| Sonnet 5 | $0.00037 | $0.00488 |
| Haiku 4.5 | $0.00019 | $0.00244 |
Grade A, and why
rum-tracking 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 6d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RUM Tracking
Guides product-analytics and RUM event tracking for web (React/Next.js) and mobile (React Native/Expo) apps. Decides what to capture, what to drop, what's PII, and how to add, audit, update, and remove tracking code without breaking downstream dashboards.
External dependency. The OTel guidance in
rules/otel-conventions.mdbuilds on theotel-instrumentationandotel-semantic-conventionsskills, which live in the dash0 agent-skills repo, not this one. That rule invokes them at runtime viaSkill()when they're installed (and skips silently otherwise) — install them alongside this skill to get their authoritative span/metric/attribute guidance.
This
SKILL.mdis a thin index. Detailed rules live inrules/*.mdand load on demand. Worked examples live inreferences/*.md. Literal scaffolding lives intemplates/*.md.
Mode Detection
Parse $1 as the mode.
State the detected mode in one line before continuing.
| Mode | Default | Trigger |
|---|---|---|
guide |
yes | "what should I track", "is this worth tracking", default if no mode |
implement |
"add tracking", "instrument this", "track this event" | |
audit |
"audit tracking", "review analytics", "find tracking issues" | |
remove |
"remove tracking", "delete this event", "deprecate", "/rm-tracking" | |
plan |
"tracking plan", "design event schema", "what events do we need" |
If $1 is a target file or directory, treat it as the scope for audit,
implement, or remove.
Workflow by Mode
Guide mode (default)
The user is deciding whether and what to track at a specific point.
- Load
rules/what-to-track.mdandrules/what-not-to-track.md. - Cross-check the proposal against
rules/pii-and-compliance.md. - Recommend an event name + property set using
rules/event-design.md. - If the project uses OpenTelemetry RUM (Dash0 SDK Web, OTel browser /
mobile, Embrace), also apply
rules/otel-conventions.md. - Surface canonical events from
references/event-catalog.mdinstead of inventing new ones when one fits.
What ships with it
14 files beside SKILL.md 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.
- references/event-catalog.md 14 KB
- references/platforms.md 8.9 KB
- rules/audit-checklist.md 7.6 KB
- rules/event-design.md 10 KB
- rules/implementation-mobile.md 10 KB
- rules/implementation-web.md 10 KB
- rules/otel-conventions.md 16 KB
- rules/pii-and-compliance.md 11 KB
- rules/tracking-plan.md 8.8 KB
- rules/update-and-remove.md 9.2 KB
- rules/what-not-to-track.md 10 KB
- rules/what-to-track.md 10.0 KB
- templates/analytics-wrapper.template.ts 7.8 KB runs code
- templates/tracking-plan.template.yaml 6.1 KB
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.
- 6d ago First seen · 217 lines · 187 tokens per session scan A 3de4ca42b5b1
rum-tracking is a skill published in the GitHub repository mthines/agent-skills (12 stars, last pushed yesterday), licensed MIT. It adds 187 tokens to every session and 2,441 once invoked, about $0.0009 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
ego-browser
Skill "ego-browser" from citrolabs/ego-lite, covering ego-browser, quick start, common helpers, task spaces and control handoff.
temporal-developer
Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust. Use when the user is building workflows, activities, or workers with a Temporal SDK, debugging issues like non-determinism errors, stuck workflows, or activity retries, using Temporal CLI, Temporal Server, or…
x-algorithm
Write X (Twitter) posts that the For You algorithm actually rewards. Grounded in the open-sourced X recommendation system — the Grok-based transformer ranker, Phoenix retrieval, Thunder in-network store, and Grox content-understanding pipeline. Use when the user wants to write a post, thread, reply, or quote; plan a…
opencode-memory
Browse local OpenCode history: sessions, messages, plans, prompt history, and prior decisions. Use when the user says history, previous session, last time, remember, recall, plans, prior work, or when resuming/debugging repeated work where earlier OpenCode context may help. Do not use for fresh tasks or when current…
creating-explainers
Use when creating an interactive explainer - a single self-contained HTML page with hand-built Canvas figures. Handles source-file explainers, topic-driven research explainers, and mixed intake where files provide the spine and research adds support. Trigger phrases include "make an explainer", "turn this paper into…
custom-icons
Create or refine custom icon assets as native or traced SVGs and transparent PNG/WebP files. Use when the user asks for a bespoke icon or cohesive icon set, wants an image traced into a clean vector, or needs a detailed or 3D icon with transparency.