manage-lexicon

manage-lexicon is a skill for Claude Code from mixpanel/ai-plugins. It costs 209 tokens per session (1,975 once invoked), scanned A, original, Apache-2.0.

A Mixpanel skill for reviewing and maintaining the Lexicon, the catalogue of tracked events and properties. It can assess metadata quality, fill missing information, handle tags, and address data-quality issues.

In plain words
What is it for?
Use it to score Lexicon health, add missing descriptions or display names, apply tags, reset metadata, investigate type or volume problems, or manage tags.
Why use it?
It brings scattered cleanup and review work into one process so teams can find incomplete or inconsistent tracking definitions.

Skill for Claude Code

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

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is **Engine required** — resolve an engine per [`ENGINE.md`](../../ENGINE.md): one named in the conversation or loaded instructions is mandatory (not set up → offe.

Part of the mixpanel plugin — 12 skills, 23 commands shipped together

Good fit Use it to score Lexicon health, add missing descriptions or display names, apply tags, reset metadata, investigate type or volume problems, or manage tags.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/mixpanel/ai-plugins
agentmods
npx agentmods add skills/mixpanel/ai-plugins/manage-lexicon

Made for: Claude Code.

Or install mixpanel, the plugin that ships this one along with the rest of its 12 skills, 23 commands.

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 manage-lexicon

README.md
[![agentmods](https://agentmods.dev/badge/skills/mixpanel/ai-plugins/manage-lexicon.svg)](https://agentmods.dev/skills/mixpanel/ai-plugins/manage-lexicon)
Your own site
<a href="https://agentmods.dev/skills/mixpanel/ai-plugins/manage-lexicon"><img src="https://agentmods.dev/badge/skills/mixpanel/ai-plugins/manage-lexicon.svg" alt="Measured on agentmods" height="20"></a>
Per session 209 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,975 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original 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.00209 $0.01975
Opus 5 $0.00105 $0.00988
Sonnet 5 $0.00042 $0.00395
Haiku 4.5 $0.00021 $0.00198

Measured 8d ago against content hash fcd239d257c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

manage-lexicon 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 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.

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.

plugins/mixpanel/skills/manage-lexicon/SKILL.md · 152 lines

How it starts

The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Manage Lexicon

Engine required — resolve an engine per ENGINE.md: one named in the conversation or loaded instructions is mandatory (not set up → offer /mixpanel:install for it); otherwise use the Mixpanel MCP server, or offer /mixpanel:install if it's unavailable.

This skill manages a Mixpanel project's Lexicon — the registry of tracked events and properties. It scores metadata quality, bulk-enriches missing descriptions / display names / tags, resets metadata, triages data quality issues, and renames or deletes tags. It runs as a single interactive session per project; do not invoke in parallel for the same project.


Components

The skill is built from a small set of abstractions. The Execution section below tells you how to use them.

Canonical commands

Each command lives in its own file under commands/ and is loaded on demand. Match commands explicitly (user names them) or implicitly (message matches a trigger phrase below).

Command File Match if message contains any of
score-lexicon commands/score-lexicon.md score, audit, health, grade
enrich-and-tag commands/enrich-and-tag.md enrich, fill, auto-tag, generate descriptions
reset-lexicon commands/reset-lexicon.md reset, wipe, clear metadata, clear tags
review-issues commands/review-issues.md issues, drift, anomaly, data quality
manage-tags commands/manage-tags.md rename tag, delete tag, merge tags

If a message matches more than one command, show the Command menu instead.

Command menu

Shown when no command was detected or inferred.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Manage Lexicon — [Project Name] ([project_id])
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  1. Score Lexicon    — Health score (0–100), auto-offer bulk enrich
  2. Enrich & Tag     — Fill empty display names, descriptions & tags
  3. Reset Lexicon    — Clear descriptions / display names / tags
  4. Review Issues    — Triage data quality issues
  5. Manage Tags      — Rename or delete existing tags
  6. Exit
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Read the full file on GitHub · 152 lines

Files

What ships with it

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

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. 8d ago First seen · 152 lines · 209 tokens per session scan A fcd239d257c3

Subscribe to this mod's changes

manage-lexicon is a skill published in the GitHub repository mixpanel/ai-plugins (15 stars, last pushed 4d ago), licensed Apache-2.0. It adds 209 tokens to every session and 1,975 once invoked, about $0.0010 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens