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 skills add jeremylongworth-source/AgentSkills --skill analytics-instrumentation-plangit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/analytics-instrumentation-plan)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/analytics-instrumentation-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/analytics-instrumentation-plan/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/skills/jeremylongworth-source/agentskills/analytics-instrumentation-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/analytics-instrumentation-plan.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.00051 | $0.00298 |
| Opus 5 | $0.00026 | $0.00149 |
| Sonnet 5 | $0.00010 | $0.00060 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
analytics-instrumentation-plan 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 10d 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
Analytics Instrumentation Plan
Core Workflow
- Identify decisions and analyses the instrumentation must support.
- Define events, properties, identity keys, account/user relationships, source systems, and naming conventions.
- Map events to product states, backend actions, UI flows, and funnel steps.
- Add privacy, consent, PII, retention, and access considerations.
- Specify validation, QA, backfill, and monitoring checks.
- Document ownership and change-control process.
Safety Rules
- Do not collect PII, sensitive data, or regulated data without explicit policy and reviewer approval.
- Do not invent platform-specific event behavior without checking current docs when implementation depends on it.
- Do not treat unvalidated instrumentation as reliable for decisions.
Deliverable Shape
For instrumentation plans, provide:
- Decision and analysis goals
- Event taxonomy
- Property schema
- Identity and account model
- Privacy and consent notes
- Validation and QA plan
- Data quality monitoring
- Ownership and change control
References
- Read
references/analytics-instrumentation-plan-checklist.mdwhen planning analytics tracking.
What ships with it
2 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.
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.
- 10d ago First seen · 44 lines · 51 tokens per session scan A e3c31278424d
analytics-instrumentation-plan is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 8d ago), licensed MIT. It adds 51 tokens to every session and 298 once invoked, about $0.0003 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
issue-authoring
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…
idd-spec-audit
Semantic audit of the IDD instruction corpus for leaked session context, cross-file contradictions, fresh-memory completability gaps, automation blockers, and restatement-discipline drift. Use on request to audit .github/instructions, the issue-authoring skill bundle, and the installed agent entry files (CLAUDE.md…
unity-yaml-format
Inspect, explain, diff, and carefully edit Unity text-serialized files such as .unity, .prefab, .asset, and related YAML-based project files. Use when mapping class IDs and fileIDs, tracing object references, reviewing merge conflicts, or making minimal safe edits to existing UnityYAML documents.
joedevflow
Development workflow. Use when building a feature, creating an MVP, refactoring code, fixing a bug, or any task that involves writing or changing implementation code.
authos-backend-integration
Secure backend APIs with AuthOS-issued JWTs and the AuthOS Node server adapter. Use when building an API that must verify AuthOS bearer tokens, enforce JWT claims, add Express middleware, validate JWKS keys, or create a backend-owned session after a browser OAuth callback.
authos-service-management
Manage AuthOS tenant services, OAuth client credentials, redirect URIs, device activation URIs, plans, API keys, SAML settings, and checkout. Use when creating or configuring applications inside an AuthOS organization.