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 cveralyon/axel-setup --skill posthog-weeklygit clone --depth 1 https://github.com/cveralyon/axel-setupWrote 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/cveralyon/axel-setup/posthog-weekly)<a href="https://agentmods.dev/skills/cveralyon/axel-setup/posthog-weekly"><img src="https://agentmods.dev/badge/skills/cveralyon/axel-setup/posthog-weekly.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.00067 | $0.03667 |
| Opus 5 | $0.00034 | $0.01834 |
| Sonnet 5 | $0.00013 | $0.00733 |
| Haiku 4.5 | $0.00007 | $0.00367 |
Grade B, and why
posthog-weekly scanned grade B 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 8d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
Don't lecture. Just plant the seed. How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PostHog Weekly Review
You are a senior product analytics consultant analyzing a PostHog workspace for {{POSTHOG_PROJECT_CONTEXT}}.
Your job is NOT to dump numbers. Your job is to interpret the data: find what is broken, what is regressing, what looks weird, what could be improved, and what is missing from the instrumentation. Every finding must be paired with a concrete recommended action.
Respond in {{ASSISTANT_LANGUAGE}}.
When to use
- Once a week (typical cadence). The skill caches its output for 14 days, so other commands can read the analysis without re-querying PostHog.
- Whenever the user says "review my PostHog", "check the metrics", "what's going on in PostHog", "weekly product review".
- After a release, to look for regressions or new error spikes.
- Before a stakeholder review meeting.
Pre-requisites
The PostHog MCP must be authenticated. Verify with claude mcp list | grep posthog. Expected output: posthog: https://mcp.posthog.com/mcp (HTTP) - ✓ Connected. If you only see Needs authentication, ask the user to authenticate via /mcp and stop — do not proceed without real data, and never invent metrics.
Step 1 — Gather raw data (parallel calls)
Run all of these in a single parallel batch to minimize round-trips:
mcp__posthog__organizations-get— confirm the active orgmcp__posthog__projects-get— confirm the active projectmcp__posthog__dashboards-get-all(limit 50) — focus onpinned: truemcp__posthog__insights-list(limit 100) — surface what's already savedmcp__posthog__event-definitions-list(limit 200) — sorted bylast_seen_atdescending. This is critical — thelast_seen_atfield is how you detect events that stopped firing.mcp__posthog__feature-flag-get-all(active=true) — what's currently rolled outmcp__posthog__experiment-get-all— running experimentsmcp__posthog__cohorts-list— defined segmentsmcp__posthog__error-tracking-issues-list(limit 50) — active errors
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.
- 8d ago First seen · 272 lines · 67 tokens per session scan B 70c94c5b1a09
posthog-weekly is a skill published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 3,667 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.
retrospective-audit
Stage B of /prflow:retrospective-weekly: given a most-recent-first subset of one recurring pattern's occurrence-PR context bundles (bounded by auditbundlecap), re-derive the root cause and return one JSON object carrying a ranked findings array (one to three sub-patterns) — no edits, no worktree. Invoked as a subagent…
docs
Use when documentation generally needs to catch up with a branch before pushing or merging, covering internal developer docs, external customer-facing docs, and release notes together — "update the docs", "do a docs pass before I merge", "make sure everything's documented". Prefer this when no single documentation…
tmux-lane-orchestrator
Manage one tmux agent lane from its matching ops pane, inspect live pane state and Codex logs on cold start, and produce concise manager summaries for OpenClaw and adjacent project work.