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 ChrisGVE/localdata-mcp --skill cluster-analysisgit clone --depth 1 https://github.com/ChrisGVE/localdata-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/chrisgve/localdata-mcp/cluster-analysis)<a href="https://agentmods.dev/skills/chrisgve/localdata-mcp/cluster-analysis"><img src="https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/cluster-analysis/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/chrisgve/localdata-mcp/cluster-analysis"><img src="https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/cluster-analysis.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.00585 |
| Opus 5 | $0.00013 | $0.00293 |
| Sonnet 5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
cluster-analysis 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 10d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cluster Analysis
Find natural groupings in data using multiple clustering approaches, evaluate quality, and interpret results.
Steps
-
Explore features. Call
describe_databasewith the database name from$ARGUMENTS. Identify numeric columns suitable for clustering. Note any categorical columns that could provide context for interpreting clusters later. -
Extract and review data. Call
execute_queryto select the numeric feature columns. Check for nulls and extreme outliers in the sample. Note the number of observations and features. -
Run K-Means clustering. Call
analyze_clusterswith the database name, feature columns, and algorithm set to "kmeans". Start with k=3 unless domain knowledge suggests otherwise. Review the silhouette score and cluster sizes. -
Try alternative k values. If the silhouette score is below 0.5, re-run
analyze_clusterswith k=2, k=4, and k=5. Compare silhouette scores to find the optimal number of clusters. -
Run DBSCAN for comparison. Call
analyze_clusterswith algorithm set to "dbscan". This density-based approach does not require specifying k and can find irregularly shaped clusters. Compare the number of clusters found and the noise point percentage. -
Evaluate and compare. Assess both approaches:
- Silhouette scores (higher is better, above 0.5 is good)
- Cluster balance (are clusters roughly even or heavily skewed?)
- Number of noise points in DBSCAN
- Which method produces more interpretable groupings
-
Reduce dimensions for visualization. Call
reduce_dimensionswith the database name and feature columns, using PCA with 2 components. This provides a 2D representation of the clusters for interpretation. -
Interpret clusters. For the best clustering result, describe each cluster by its feature averages. Give each cluster a descriptive label based on its defining characteristics. Note which features most differentiate the clusters.
-
Present results. Provide:
- Recommended number of clusters and algorithm
- Cluster profiles with feature summaries
- Silhouette score and quality assessment
- Observations about cluster separation and overlap
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.
- 10d ago First seen · 41 lines · 26 tokens per session scan A 5965ab126164
cluster-analysis is a skill published in the GitHub repository ChrisGVE/localdata-mcp (4 stars, last pushed 27d ago), licensed Apache-2.0. It adds 26 tokens to every session and 585 once invoked, about $0.0001 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-31.
Other skills, from other repositories
wingman-mcp
Add persistent, interactive task plan management to your agent. Wingman tracks plans and tasks across a long conversation — Claude creates plans, ticks tasks after completing work, and a live panel renders inline in the chat. Install the MCP server first, then use these tools to manage plans and tasks throughout any…
liveagent-code-review
Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation. Use when the user asks for code review, invokes the Code Review action from Git Review, or explicitly mentions this skill.
skills-creator
Create or update LiveAgent runtime skills. Use when you need to summarize a workflow into a skill, write it into the fixed user skills root, validate it, package it, or refine a skill's references for LiveAgent's SkillsManager flow.
skills-installer
Install, list enabled, validate, or package LiveAgent skills. Use when you need to inspect the skills enabled in the current conversation, import a local skill directory or package, search/install from ClawHub, install from a GitHub repo/tree URL, or reconcile conflicts during an upgrade.
triaging-incidents
Creating, triaging, updating, and analyzing ServiceNow incidents. Assess severity, check affected CIs, find related incidents, and recommend assignments. Use when the user mentions incidents, INC numbers, outages, service disruptions, ticket creation, triage, priority, severity, ITSM operations, SLA breaches…
reviewing-update-sets
Reviewing, analyzing, and comparing ServiceNow update sets before promotion. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sysupdatexml, customer updates, "what changed in this update set," or…