feature-usage-feed

feature-usage-feed is a skill for Claude Code from PostHog/ai-plugin. It costs 123 tokens per session (6,583 once invoked), scanned A, original, no licence file.

A setup for an automated evaluation that identifies common ways people use a PostHog feature and sends the findings to Slack. An LLM judge is an AI-based evaluator that reviews and labels examples at scale.

In plain words
What is it for?
Use it to extract feature use cases and stream the evaluation results to a Slack channel.
Why use it?
It helps teams see how an AI or language-model feature is being used in production without reviewing every example manually.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the posthog plugin — 175 skills, 3 commands, 1 agent, 3 hooks, 1 MCP server shipped together

Good fit Use it to extract feature use cases and stream the evaluation results to a Slack channel.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/posthog/ai-plugin/feature-usage-feed
Install

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.

Any agent
npx skills add PostHog/ai-plugin --skill feature-usage-feed
Clone the repo
git clone --depth 1 https://github.com/PostHog/ai-plugin

Made for: Claude Code.

Or install posthog, the plugin that ships this one along with the rest of its 175 skills, 3 commands, 1 agent, 3 hooks, 1 MCP server.

Wrote 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.

agentmods badge for feature-usage-feed

README.md
[![agentmods](https://agentmods.dev/badge/skills/posthog/ai-plugin/feature-usage-feed/github.svg)](https://agentmods.dev/skills/posthog/ai-plugin/feature-usage-feed)
Your own site
<a href="https://agentmods.dev/skills/posthog/ai-plugin/feature-usage-feed"><img src="https://agentmods.dev/badge/skills/posthog/ai-plugin/feature-usage-feed/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.

agentmods 80×15 button for feature-usage-feed

Your own site · 80×15
<a href="https://agentmods.dev/skills/posthog/ai-plugin/feature-usage-feed"><img src="https://agentmods.dev/badge/skills/posthog/ai-plugin/feature-usage-feed.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 123 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,583 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00123 $0.06583
Opus 5.5 $0.00049 $0.02633
Sonnet 5.5 $0.00025 $0.01317
Haiku 4.5 $0.00012 $0.00658

Measured 1mo ago against content hash 04803658d2fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature-usage-feed 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 1mo 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.

skills/feature-usage-feed/SKILL.md · 455 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 1mo ago Changed · +5 lines 04803658d2fe
  2. 1mo ago Changed · +4 lines e3646eaac0fa
  3. 1mo ago First seen · 446 lines · 123 tokens per session scan A ebfdfe17e50a

Subscribe to this mod's changes

feature-usage-feed is a skill published in the GitHub repository PostHog/ai-plugin (96 stars, last pushed yesterday), with no licence file. It adds 123 tokens to every session and 6,583 once invoked, about $0.0005 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-09-03.

Related

Other skills, from other repositories

domscribe

Work with Domscribe — the pixel-to-code bridge. Use when setting up, initializing, or configuring Domscribe for a project, OR when editing or modifying UI components (React, Vue, Next.js, Nuxt), implementing features from captured UI annotations, querying runtime context for source locations, exploring component…

patchorbit/domscribe · 94 tokens

writing-extensions

Guide for authoring a new in-process MCP tool extension for gerrit-mcp-server. Use when a user wants to add new Gerrit tools, port a standalone plugin MCP server into the extension framework, or needs a worked example of the ExtensionContext API.

GerritCodeReview/gerrit-mcp-server · 57 tokens

gerrit-task-query

Use when asked to check, list, or act on tasks for a Gerrit change. Triggers on phrases like "what tasks are blocking", "which tasks are actionable", "check task status", "what do I need to do for this change", "what is blocking this change".

GerritCodeReview/gerrit-mcp-server · 64 tokens

gerrit-workflow

This skill should be used when the user asks to "submit a change to Gerrit", "push for review", "upload a patch", "update a change in Gerrit", "add a patch set", "work with Gerrit", "push to refs/for", "fix a missing Change-Id", "amend a Gerrit change", or any task involving git operations in a repository hosted on…

GerritCodeReview/gerrit-mcp-server · 123 tokens

find-dependencies

Find all dependencies of a Gerrit change or set of changes — both explicit Depends-on annotations (parsed by the depends-on plugin) and implicit git-chain parents. Use when asked: what does this change depend on, what is blocking this change, show me the dependency chain, are all dependencies merged, which changes…

GerritCodeReview/gerrit-mcp-server · 71 tokens

wavedash

Use when building, integrating, testing, uploading, publishing, or preparing a browser game for Wavedash, including CLI setup, Wavedash SDK features, multiplayer, achievements, leaderboards, cloud saves, player identity, user-generated content, store metadata, monetization, and content guidelines.

wvdsh/ai · 63 tokens