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 agentmods add commands/mixpanel/ai-plugins/score-lexicongit clone --depth 1 https://github.com/mixpanel/ai-pluginsWrote 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/commands/mixpanel/ai-plugins/score-lexicon)<a href="https://agentmods.dev/commands/mixpanel/ai-plugins/score-lexicon"><img src="https://agentmods.dev/badge/commands/mixpanel/ai-plugins/score-lexicon.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 | $0.00000 | $0.01239 |
| Opus 5 | $0.00000 | $0.00620 |
| Sonnet 5 | $0.00000 | $0.00248 |
| Haiku 4.5 | $0.00000 | $0.00124 |
Grade A, and why
score-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 4d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command — Score Lexicon
Session reads:
event_list,event_details_cache,property_names,volume_rank_mapSession writes:event_list,event_details_cache,property_names,property_details_cache,volume_rank_map
Audit Lexicon metadata coverage and compute a health score (0–100). Self-contained pipeline: fetch → audit → score → report. Execute silently — no phase announcements.
Phase 1 — Fetch Schema
Load the events, properties, and volume ranking the audit needs.
Ensure the required Session reads are loaded; load any that aren't.
- Events + metadata. Load event metadata for the full project.
- Volume ranking. Run the payload in
assets/volume-ranking-query.json. Parse the response intovolume_rank_map: { event_name: { volume, rank } }. If the query fails, proceed withvolume_rank_map = {}— downstream degrades gracefully (the score still renders; severity scoring inreview-issuesskips the volume tiebreaker). - Properties + metadata. Load property metadata for event properties and user properties separately. Merge into
property_names: { event: [...], user: [...] }andproperty_details_cache.
Phase 2 — Audit Event Metadata
Score every event in the working set against the four metadata fields plus hygiene.
| Field | Pass condition |
|---|---|
description |
Non-null, non-empty |
display_name |
Non-null AND differs from raw event name |
verified |
true |
tags |
Non-empty array |
hygiene |
Zero 7-day volume → must be hidden/dropped. If not → ⚠️ |
Compute per-field coverage: (pass count) / (working set size) × 100.
Collect zero-metadata events (all four of description, display_name, verified, tags fail).
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.
- 4d ago First seen · 148 lines · 0 tokens per session scan A aeb38d2cd0cd
score-lexicon is a command published in the GitHub repository mixpanel/ai-plugins (15 stars, last pushed 10d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,239 tokens. 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.