armor-quality

A data-quality tool that measures tables and checks whether their values follow rules. It can track row counts, missing-value rates, unique values, freshness, allowed values, patterns, and custom SQL conditions.

In plain words
What is it for?
Use it to add missing-value or uniqueness checks, create row-count and freshness measurements, validate allowed values or patterns, and view quality status.
Why use it?
It replaces informal inspection with repeatable checks that can show whether data is complete, unique, valid, and up to date. This makes the current quality of a table easier to review.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/anomalyarmor/agents/quality
Any agent
npx skills add anomalyarmor/agents --skill quality
Clone the repo
git clone --depth 1 https://github.com/anomalyarmor/agents

Made for: Claude Code, Codex.

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 951 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00039 $0.00951
Opus 5 $0.00019 $0.00476
Sonnet 5 $0.00008 $0.00190
Haiku 4.5 $0.00004 $0.00095

Measured yesterday against content hash cfee0af11cb6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

armor-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 yesterday.

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/quality/SKILL.md · 149 lines

How it starts

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

Data Quality

Set up and manage data quality checks including metrics (row counts, null rates, distinct counts) and validity rules (null checks, uniqueness, custom expressions).

Prerequisites

  • AnomalyArmor API key configured (~/.armor/config.yaml or ARMOR_API_KEY env var)
  • Python SDK installed (pip install anomalyarmor)

When to Use

  • "Add a null check to the email column"
  • "Create a row count metric for orders"
  • "What metrics exist for this table?"
  • "Add a uniqueness check on customer_id"
  • "Show data quality status"
  • "Set up a freshness metric"

Concepts

Metrics

Metrics track quantitative measurements over time:

  • row_count: Number of rows in a table
  • null_rate: Percentage of null values in a column
  • distinct_count: Number of unique values
  • freshness: Time since last update

Validity Rules

Rules that validate data integrity:

  • NOT_NULL: Column must not contain nulls
  • UNIQUE: Column values must be unique
  • ACCEPTED_VALUES: Column values must be in allowed list
  • REGEX: Column values must match pattern
  • CUSTOM: Custom SQL expression

Steps

Creating a Metric

  1. Get the asset ID for the target table
  2. Choose metric type (row_count, null_rate, distinct_count, etc.)
  3. Call client.metrics.create() with appropriate parameters
  4. Optionally trigger immediate capture with client.metrics.capture()

Creating a Validity Rule

  1. Get the asset ID for the target table
  2. Choose rule type (NOT_NULL, UNIQUE, ACCEPTED_VALUES, etc.)
  3. Call client.validity.create() with column and rule parameters
  4. Optionally run immediate check with client.validity.check()

Example Usage

List Existing Metrics

from anomalyarmor import Client

client = Client()

# Get metrics summary
summary = client.metrics.summary("asset-uuid")
print(f"Total metrics: {summary.total_metrics}")
print(f"Failing metrics: {summary.failing_count}")

# List all metrics
metrics = client.metrics.list("asset-uuid")
for m in metrics:
    print(f"  {m.metric_type}: {m.name} ({m.status})")

Read the full file on GitHub · 149 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. yesterday First seen · 149 lines · 39 tokens per session scan A cfee0af11cb6

Subscribe to this mod's changes

armor-quality is a skill published in the GitHub repository anomalyarmor/agents (1 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 951 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens