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 data-qualitygit 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/data-quality)<a href="https://agentmods.dev/skills/chrisgve/localdata-mcp/data-quality"><img src="https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/data-quality/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/data-quality"><img src="https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/data-quality.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.00655 |
| Opus 5 | $0.00015 | $0.00328 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
data-quality 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 9d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Quality Assessment
Perform a comprehensive data quality audit covering completeness, consistency, validity, and uniqueness.
Steps
-
Connect if needed. If
$ARGUMENTSis a file path, callconnect_databaseto load it. If it is a database name, proceed directly. Calldescribe_databaseto list all tables and row counts. -
Profile each table. For each table (or the primary tables if many), call
describe_tableto get column types, nullability, and cardinality. Callget_data_quality_reportfor detailed quality metrics. -
Assess completeness. Call
execute_queryto compute null percentages per column. Classify:- Complete (< 1% null): no action needed
- Minor gaps (1-10% null): note but likely manageable
- Significant gaps (10-30% null): flag for imputation or exclusion decisions
- Severe gaps (> 30% null): column may be unusable without careful treatment
-
Check uniqueness. For each column, call
execute_queryto compare distinct count against total count. Identify:- Candidate keys (100% unique)
- High-cardinality categoricals (many unique values but not keys)
- Suspicious duplicates (IDs that should be unique but are not)
-
Validate value ranges. Call
execute_queryto compute min, max, mean, and percentiles for numeric columns. Flag:- Impossible values (negative ages, future dates in historical data, percentages > 100)
- Extreme outliers (values beyond 3 IQR from quartiles)
- Suspicious constants (columns with a single value)
-
Check consistency. Look for:
- Mixed data types within columns (numbers stored as strings)
- Inconsistent formats (date formats, case sensitivity, encoding)
- Referential integrity (foreign keys with no matching parent)
- Contradictory records (same entity with conflicting attribute values)
-
Report findings. Present a structured quality scorecard:
- Overall data health score (percentage of columns with no issues)
- Per-column quality summary: completeness, uniqueness, validity
- Ranked list of issues from most to least severe
- Impact assessment: which issues would affect which types of analysis
- Remediation suggestions for each issue category
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.
- 9d ago First seen · 51 lines · 30 tokens per session scan A cfca1600383d
data-quality is a skill published in the GitHub repository ChrisGVE/localdata-mcp (4 stars, last pushed 26d ago), licensed Apache-2.0. It adds 30 tokens to every session and 655 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.
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…