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 amplitude/mcp-marketplace --skill event-description-generatorgit clone --depth 1 https://github.com/amplitude/mcp-marketplaceWrote 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/amplitude/mcp-marketplace/event-description-generator)<a href="https://agentmods.dev/skills/amplitude/mcp-marketplace/event-description-generator"><img src="https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/event-description-generator/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/amplitude/mcp-marketplace/event-description-generator"><img src="https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/event-description-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00077 | $0.01852 |
| Opus 5 | $0.00039 | $0.00926 |
| Sonnet 5 | $0.00015 | $0.00370 |
| Haiku 4.5 | $0.00008 | $0.00185 |
Grade A, and why
event-description-generator 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 12d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event Description Generator
Run this skill as an orchestrator only. Do not perform per-event filtering, repo search, or description-writing logic in this skill body. Delegate chunk processing to the event-descriptions-worker subagent.
Workflow
- Resolve project input (
projectIdor project name) - Create a run ID with short git SHA (
<projectId>-<sha>) - Create run directories under
runs/ - Determine cursor plan (
cursorStart,maxEvents, chunk size) - Spawn
event-descriptions-workersubagents for cursor chunks - Collect worker summaries + output paths
- Compress the run into a single CSV
- Report concise progress and next cursor
Execution Rules
- Keep this skill as a dispatcher; the worker does the heavy lifting.
- Do not call
set_event_metadatafrom this skill. - Do not manually re-implement worker filtering/search logic here.
- Preserve user control over scope (project, cursor range, chunk size, parallelism).
Prerequisites
The user must provide either:
projectId, or- project name to resolve.
If neither is provided, stop and ask.
Phase 1: Resolve Project
1.1 If projectId is provided
Use it directly.
1.2 If project name is provided
Call get_context and resolve the name to a single projectId.
- If exactly one clear match exists, continue with that ID.
- If multiple matches exist, ask the user to choose.
- Do not choose an ambiguous match on behalf of the user.
1.3 If project name is not provided
Prompt the user to input the project name or ID and halt.
Phase 2: Build Cursor Plan
Default values unless the user specifies otherwise:
cursorStart:0maxEvents:400eventsPerWorker:50maxParallelWorkers:4
For maxEvents:
- Compute total chunks as
ceil(maxEvents / eventsPerWorker). - Process at most
maxEventsevents starting atcursorStart. - For the final chunk, pass a reduced
eventsPerWorkerif needed to avoid exceedingmaxEvents.
For each chunk:
What ships with it
3 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.
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.
- 12d ago First seen · 249 lines · 77 tokens per session scan A 4931b0415802
event-description-generator is a skill published in the GitHub repository amplitude/mcp-marketplace (35 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 1,852 once invoked, about $0.0004 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…
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…