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 celticht32/Enterprise-Analytics-MCP --skill cb-analytics-admingit clone --depth 1 https://github.com/celticht32/Enterprise-Analytics-MCPWrote 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/celticht32/enterprise-analytics-mcp/cb-analytics-admin)<a href="https://agentmods.dev/skills/celticht32/enterprise-analytics-mcp/cb-analytics-admin"><img src="https://agentmods.dev/badge/skills/celticht32/enterprise-analytics-mcp/cb-analytics-admin.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.1 | $0.00075 | $0.00777 |
| Opus 5 | $0.00037 | $0.00388 |
| Sonnet 5 | $0.00015 | $0.00155 |
| Haiku 4.5 | $0.00007 | $0.00078 |
Grade A, and why
cb-analytics-admin 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 6d 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.
This is a copy
91% identical to cb-analytics-admin — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics service admin
You have 7 tools for runtime management.
Status snapshot (read-only, safe)
get_service_status(cluster)— overall service state, replica lag, authorised node listget_ingestion_status(cluster)— per-link ingestion state, pending opsget_active_requests(cluster)— what's running right nowget_completed_requests(client_context_id=None, cluster)— recent history; passclient_context_idto filter to one request
Diagnostic workflow
When a user says "queries are slow" or "ingestion looks stuck":
get_service_status— is the service even healthy? WatchccRevLag(replication lag).get_ingestion_status— for each link, look atpendingOperations. A non-zero pending count after a quiet period usually means a stuck link.get_active_requests— long-running queries appear here withelapsedTime. Anything over a few seconds is suspect.get_completed_requests— look for a pattern of errors or unusually long durations.
Destructive operations (use with care)
cancel_request(client_context_id, cluster)— abort one in-flight query. Get the id fromget_active_requests.restart_node(cluster)— restart only the Analytics process on the local node. May briefly disrupt queries routed to that node.restart_service(cluster)— cluster-wide Analytics restart. All active queries fail. Don't suggest this lightly; warn the user.
Confirmation patterns
When the user asks to cancel or restart anything, always confirm by naming what you're about to do, with the specific request id or cluster name. Example:
Cancel request
cb-12345on clusterprod? This will return an error to whichever client issued it.
After they confirm, run the tool and report success or failure based on
the returned ok field.
What to avoid
- Don't restart the service to "fix" a slow query — try cancelling it first.
- Don't call
cancel_requeston aclient_context_idthat's already completed; it's a no-op but generates a confusing error. - Don't poll
get_active_requestsaggressively (e.g. every second). Once per few seconds is fine.
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.
- 6d ago First seen · 85 lines · 75 tokens per session scan A 37dacfe12ad2
cb-analytics-admin is a skill published in the GitHub repository celticht32/Enterprise-Analytics-MCP (0 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 777 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to cb-analytics-admin, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.