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 anomaly-detectiongit 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/anomaly-detection)<a href="https://agentmods.dev/skills/chrisgve/localdata-mcp/anomaly-detection"><img src="https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/anomaly-detection/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/anomaly-detection"><img src="https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/anomaly-detection.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.00030 | $0.00502 |
| Opus 5 | $0.00015 | $0.00251 |
| Sonnet 5 | $0.00006 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
anomaly-detection 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 11d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Anomaly Detection
Identify unusual observations in the data using appropriate outlier detection algorithms.
Steps
-
Explore features. Call
describe_databasewith the database name from$ARGUMENTS. Identify numeric columns suitable for anomaly detection. Callget_data_quality_reportto check for missing values and understand baseline distributions. -
Extract and inspect data. Call
execute_queryto select the feature columns. Check the number of rows and features. Note the expected contamination rate if the user has a prior estimate; otherwise default to 5%. -
Select the algorithm. Choose based on data characteristics:
- Isolation Forest: good general-purpose detector, works well up to ~50 features, fast on large datasets
- Local Outlier Factor: better when anomalies are defined by local density differences (normal behavior varies across data regions)
-
Run anomaly detection. Call
detect_anomalieswith the database name, feature columns, and selected algorithm. Review the results: number of anomalies flagged, anomaly scores distribution, and the score threshold used. -
Inspect the anomalies. Call
execute_queryto retrieve the flagged anomalous rows. Examine what makes them unusual: which feature values are extreme? Are there common patterns among the anomalies? -
Visualize in reduced dimensions. Call
reduce_dimensionswith PCA (2 components) on the same features. Map anomaly labels onto the 2D representation to see whether anomalies cluster together or are scattered. -
Assess sensitivity. If the contamination rate strongly affects results, note this. Report how the number of flagged anomalies changes with different thresholds.
-
Present results. Provide:
- Algorithm used and rationale
- Number of anomalies detected (count and percentage)
- Characterization of anomalies: common traits, most extreme cases
- Anomaly score distribution for context
- Recommendations: investigate flagged records, adjust detection parameters, or monitor for recurring anomaly patterns
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.
- 11d ago First seen · 36 lines · 30 tokens per session scan A 76a700211c15
anomaly-detection is a skill published in the GitHub repository ChrisGVE/localdata-mcp (4 stars, last pushed 27d ago), licensed Apache-2.0. It adds 30 tokens to every session and 502 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-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.
building-glamorous-tuis
Build terminal UIs with Charmbracelet (Bubble Tea, Lip Gloss, Gum). Use when: Go TUI, shell prompts/spinners, "make CLI prettier", adaptive layouts, async rendering, focus state machines, sparklines, heatmaps, kanban boards, SSH apps.
pr-alignment-loop
Iterate a PR to its final form by running two opposing reviewer droids (reviewer-robustness and reviewer-minimalist) in a bounded back-and-forth loop. The main orchestrator synthesizes their feedback, makes edits, runs tests, and stops when both approve, on stagnation, or after 3 rounds. Use when the user asks to…