validate-data

validate-data is a skill for Claude Code from nota-america/forgecat-agent-profiles. It costs 55 tokens per session (3,275 once invoked), scanned A, a copy of validate-data, Apache-2.0.

A review process for checking whether an analysis is accurate, methodologically sound, and fairly interpreted before it is shared. It can examine reports, notebooks, spreadsheets, SQL queries, results, charts, and their underlying data.

In plain words
What is it for?
Use it to review an analysis, validate query results, check assumptions and possible bias, and identify improvements before presenting findings.
Why use it?
It helps catch incorrect calculations, unclear metric definitions, unsuitable data, hidden exclusions, and conclusions that the evidence does not support.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it to review an analysis, validate query results, check assumptions and possible bias, and identify improvements before presenting findings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nota-america/forgecat-agent-profiles/validate-data
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 nota-america/forgecat-agent-profiles --skill validate-data
Clone the repo
git clone --depth 1 https://github.com/nota-america/forgecat-agent-profiles

Made for: Claude Code.

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 validate-data

README.md
[![agentmods](https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/validate-data/github.svg)](https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/validate-data)
Your own site
<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/validate-data"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/validate-data/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 validate-data

Your own site · 80×15
<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/validate-data"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/validate-data.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,275 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 98% copy Near-identical to another mod 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.00055 $0.03275
Opus 5 $0.00028 $0.01638
Sonnet 5 $0.00011 $0.00655
Haiku 4.5 $0.00006 $0.00328

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

Security

Grade A, and why

validate-data 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 8d 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.

Origin

This is a copy

98% identical to validate-data — 10 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.

profiles/anthropics/knowledge-work-plugins/anthropics_knowledge-work-plugins_data/for-claude/.claude/skills/validate-data/SKILL.md · 388 lines

How it starts

The opening of the file, as written. The whole thing — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/validate-data - Validate Analysis Before Sharing

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (.forgecat/profiles/@forgecat/anthropics_knowledge-work-plugins_data/CONNECTORS.md).

Review an analysis for accuracy, methodology, and potential biases before sharing with stakeholders. Generates a confidence assessment and improvement suggestions.

Usage

/validate-data <analysis to review>

The analysis can be:

  • A document or report in the conversation
  • A file (markdown, notebook, spreadsheet)
  • SQL queries and their results
  • Charts and their underlying data
  • A description of methodology and findings

Workflow

1. Review Methodology and Assumptions

Examine:

  • Question framing: Is the analysis answering the right question? Could the question be interpreted differently?
  • Data selection: Are the right tables/datasets being used? Is the time range appropriate?
  • Population definition: Is the analysis population correctly defined? Are there unintended exclusions?
  • Metric definitions: Are metrics defined clearly and consistently? Do they match how stakeholders understand them?
  • Baseline and comparison: Is the comparison fair? Are time periods, cohort sizes, and contexts comparable?

2. Run the Pre-Delivery QA Checklist

Work through the checklist below — data quality, calculation, reasonableness, and presentation checks.

3. Check for Common Analytical Pitfalls

Systematically review against the detailed pitfall catalog below (join explosion, survivorship bias, incomplete period comparison, denominator shifting, average of averages, timezone mismatches, selection bias).

4. Verify Calculations and Aggregations

Where possible, spot-check:

  • Recalculate a few key numbers independently
  • Verify that subtotals sum to totals
  • Check that percentages sum to 100% (or close to it) where expected
  • Confirm that YoY/MoM comparisons use the correct base periods
  • Validate that filters are applied consistently across all metrics

Read the full file on GitHub · 388 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. 8d ago First seen · 388 lines · 55 tokens per session scan A 5f9cee507ff2

Subscribe to this mod's changes

validate-data is a skill published in the GitHub repository nota-america/forgecat-agent-profiles (66 stars, last pushed yesterday), licensed Apache-2.0. It adds 55 tokens to every session and 3,275 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to validate-data, differing in 10 lines, and is treated as a copy.