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 runxhq/runx --skill product-analyticsgit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/product-analytics)<a href="https://agentmods.dev/skills/runxhq/runx/product-analytics"><img src="https://agentmods.dev/badge/skills/runxhq/runx/product-analytics/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/runxhq/runx/product-analytics"><img src="https://agentmods.dev/badge/skills/runxhq/runx/product-analytics.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.00704 |
| Opus 5.5 | $0.00013 | $0.00282 |
| Sonnet 5.5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
product-analytics 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 5d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product analytics
Explain where a defined product journey loses people or accounts, what the
retention evidence shows, and which measurement or product change to consider.
This skill covers activation and product usage. organic-growth owns search and
acquisition strategy; it may consume the relevant findings.
analyze accepts supplied governed aggregate counts. Retrieve a saved insight
through a selected PostHog connector, or use another provider, before invoking
this skill. Preserve the actual report and its source digest; do not invent counts
to fit the input. This runner does not query a provider, execute SQL, capture
events, change instrumentation or create tasks.
Measurement admission
Each report carries the definition its own source was computed under: product, timezone, person/account identity, cohort, filters, funnel rule and retention rule. Read it from that report's saved query; never copy one report's definition onto another. Funnel counts must count the same eligible entities through ordered steps, not independent event totals. Retention needs an explicit eligible cohort and return period. Mark incomplete provider results incomplete. Retain observation time; a cached PostHog result is not fresh merely because its HTTP read happened today.
The pure calculation step preserves counts and computes rates. Zero eligible
entities produce null, not a measured 0% conversion or retention rate. Ordered
counts cannot increase and retained entities cannot exceed the eligible cohort.
Compare a baseline only when its definition equals the current definition field
for field, with the same ordered events and retention period over an
equal-duration, nonoverlapping window. Rate changes are percentage points, never
mislabeled relative percentage lift. Missing denominators, incompatible
definitions or incomplete reports withhold recommendations and expose the
measurement gap.
Interpretation
Use the deterministic rates; do not replace or round them into different facts. Distinguish observations, hypotheses and actions. Concentrate on the consequential drop-off, plausible instrumentation problems and a small next experiment. A change between periods does not establish causality or statistical significance. Counts alone cannot establish sample comparability, seasonality or experiment validity. Do not average cohort percentages or claim significance without the actual method and experiment evidence. State those limits when relevant.
What ships with it
10 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.
- fixtures/analyzes-activation.yaml 2.8 KB
- fixtures/composes-in-graph.yaml 1.1 KB
- fixtures/holds-invalid-funnel.yaml 1.1 KB
- fixtures/holds-mismatched-definition.yaml 1.9 KB
- fixtures/support/composed.graph 1.0 KB
- fixtures/withholds-unbound-action.yaml 2.0 KB
- product-analytics.mjs 4.7 KB runs code
- product-analytics.test.mjs 5.0 KB runs code
- references/catalog.md 161 B
- run.yaml 15 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.
- 5d ago First seen · 68 lines · 32 tokens per session scan A f404b1cfcecf
product-analytics is a skill published in the GitHub repository runxhq/runx (103 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 704 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-10-12.
Other skills, from other repositories
dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.
dd-report-format
Standard output format for due diligence analysis reports. Use when producing your final analysis to ensure consistency across all specialist agents.
dd-risk-scoring
Calculate weighted risk scores from specialist agent reports. Use when synthesizing multiple due diligence reports into an overall investment risk assessment.
dd-sourcing
Document sources properly for due diligence reports. Use when citing any external data, ensuring full traceability and auditability of findings.
dd-verification
Verify claims in pitch decks and founder statements using multiple independent sources. Use when analyzing any claim about market size, traction, team background, or competitive positioning.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.