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 skills/apolloio/apollo-mcp-plugin/analyticsnpx skills add apolloio/apollo-mcp-plugin --skill analyticsgit clone --depth 1 https://github.com/apolloio/apollo-mcp-pluginWhat 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.00035 | $0.02219 |
| Opus 5 | $0.00017 | $0.01110 |
| Sonnet 5 | $0.00007 | $0.00444 |
| Haiku 4.5 | $0.00003 | $0.00222 |
Grade A, and why
analytics 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 2d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics
Answer any sales performance question using Apollo's analytics data. The user asks a question via "$ARGUMENTS".
Examples
/apollo:analytics How many emails did I send last 30 days?/apollo:analytics Show me team call connect rate this quarter by rep/apollo:analytics What's our email reply rate week over week for this year?/apollo:analytics Break down pipeline and won amount by opportunity stage all time/apollo:analytics Which sequences have the highest reply rate in the last 6 months?/apollo:analytics Show me activity summary — emails, calls, meetings, tasks — for each rep this quarter/apollo:analytics How are calls trending by day of week over the last 3 months?/apollo:analytics Show me emails sent vs replied broken down by contact stage and email type
Step 1 — Interpret the Question
Parse "$ARGUMENTS" to determine the following parameters:
Metrics
Select 1–15 metrics that match what the user is asking about. Always include the rate/percent version alongside raw counts when the user asks about performance.
Email
num_emails_sent, num_emails_delivered, num_emails_opened, num_emails_clicked, num_emails_replied, num_emails_bounced, num_emails_unsubscribed, percent_emails_replied, num_contacts_emailed, num_contacts_opened, num_contacts_replied
Calls
num_phone_calls, num_phone_calls_completed, num_phone_calls_connect, num_phone_calls_connect_positive, num_phone_calls_connect_negative, num_phone_calls_connect_neutral, percent_phone_calls_connect, avg_phone_call_duration, num_contacts_called
Key distinctions:
num_phone_calls_completed= all logged attemptsnum_phone_calls_connect= recipient actually answerednum_phone_calls_connect_positive/negative/neutral= connected calls by outcome sentiment
Meetings
num_all_meetings_scheduled, num_meetings_held, num_all_meetings_rescheduled, num_calendar_events_scheduled, num_calendar_events_cancelled, num_all_meetings_scheduled_via_email, num_all_meetings_scheduled_via_call
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.
- 2d ago First seen · 189 lines · 35 tokens per session scan A 21cca0079298
analytics is a skill published in the GitHub repository apolloio/apollo-mcp-plugin (19 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 2,219 once invoked, about $0.0002 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…