anomaly-detection

anomaly-detection is a skill for Claude Code from ChrisGVE/localdata-mcp. It costs 30 tokens per session (502 once invoked), scanned A, original, Apache-2.0.

An anomaly detection workflow finds observations that differ unusually from the rest of a dataset, using Isolation Forest or Local Outlier Factor.

In plain words
What is it for?
Use it to prepare numeric features, choose an outlier-detection method, flag unusual observations, review anomaly scores, and inspect the flagged records.
Why use it?
It helps locate unusual records or suspicious patterns that may be missed by ordinary summaries.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the localdata-mcp plugin — 18 skills, 11 agents, 1 MCP server shipped together

Good fit Use it to prepare numeric features, choose an outlier-detection method, flag unusual observations, review anomaly scores, and inspect the flagged records.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chrisgve/localdata-mcp/anomaly-detection
Install

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.

Any agent
npx skills add ChrisGVE/localdata-mcp --skill anomaly-detection
Clone the repo
git clone --depth 1 https://github.com/ChrisGVE/localdata-mcp

Made for: Claude Code.

Or install localdata-mcp, the plugin that ships this one along with the rest of its 18 skills, 11 agents, 1 MCP server.

Wrote 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.

agentmods badge for anomaly-detection

README.md
[![agentmods](https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/anomaly-detection/github.svg)](https://agentmods.dev/skills/chrisgve/localdata-mcp/anomaly-detection)
Your own site
<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.

agentmods 80×15 button for anomaly-detection

Your own site · 80×15
<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>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 502 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 11d ago against content hash 76a700211c15, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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.

skills/modeling/anomaly-detection/SKILL.md · 36 lines

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

  1. Explore features. Call describe_database with the database name from $ARGUMENTS. Identify numeric columns suitable for anomaly detection. Call get_data_quality_report to check for missing values and understand baseline distributions.

  2. Extract and inspect data. Call execute_query to 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%.

  3. 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)
  4. Run anomaly detection. Call detect_anomalies with the database name, feature columns, and selected algorithm. Review the results: number of anomalies flagged, anomaly scores distribution, and the score threshold used.

  5. Inspect the anomalies. Call execute_query to retrieve the flagged anomalous rows. Examine what makes them unusual: which feature values are extreme? Are there common patterns among the anomalies?

  6. Visualize in reduced dimensions. Call reduce_dimensions with PCA (2 components) on the same features. Map anomaly labels onto the 2D representation to see whether anomalies cluster together or are scattered.

  7. Assess sensitivity. If the contamination rate strongly affects results, note this. Report how the number of flagged anomalies changes with different thresholds.

  8. 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

Read the full file on GitHub · 36 lines

Changes

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.

  1. 11d ago First seen · 36 lines · 30 tokens per session scan A 76a700211c15

Subscribe to this mod's changes

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.

Related

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…

adeoluwaadesina/wingman-mcp · 68 tokens

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.

Stack-Cairn/LiveAgent · 54 tokens

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.

Stack-Cairn/LiveAgent · 53 tokens

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.

Stack-Cairn/LiveAgent · 62 tokens

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.

nikships/skills-registry · 65 tokens

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…

nikships/skills-registry · 122 tokens