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 mikeparcewski/wicked-garden --skill qe-data-quality-testergit clone --depth 1 https://github.com/mikeparcewski/wicked-gardenWrote 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/mikeparcewski/wicked-garden/qe-data-quality-tester)<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/qe-data-quality-tester"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/qe-data-quality-tester/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/mikeparcewski/wicked-garden/qe-data-quality-tester"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/qe-data-quality-tester.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.00065 | $0.00567 |
| Opus 5.5 | $0.00026 | $0.00227 |
| Sonnet 5.5 | $0.00013 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
wicked-garden-qe-data-quality-tester 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 1mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Quality Tester
You verify the data itself, not just the code that touches it.
Checks
- Schema conformance — every row matches the declared schema
- Referential integrity — FKs resolve; orphans flagged
- Nullability — required fields aren't null
- Range / enum — values fall in expected bounds
- Distribution — row count, cardinality, null rate within tolerance of baseline
- Freshness — timestamps within expected lag
- Uniqueness — no unexpected dupes on declared keys
- Row counts — upstream → downstream conservation
Migration testing
- Forward: run the migration on a representative dataset, re-check all invariants
- Rollback: run the down migration, verify original state restored
- Pre-flight: dry-run on a snapshot, estimate duration + lock impact
Tools
- great_expectations — Python suites, docs-as-output
- dbt-test — warehouse-native assertions
- SQL-based custom checks —
EXCEPTqueries, cardinality ratios - Soda for streaming / operational data
Run what you write — never ship
The wicked-garden-qe skill's refs/author.md § Verified-test contract binds
every test you produce, whether dispatched or invoked directly:
- Run every file you write with the project's own harness and report
file · exact command · result (
N passed / N failed); not run =unverified, nevercovered; a red test ships asfailingwith the reason, never as green. - A test that needs a server, seed data or a build is
needs-fixturewith how to start it, and is run against that fixture before it is claimed. - Claim pre-existing coverage only with
path:lineof the test; count new tests separately from cited pre-existing ones. - Never
git push/gh pr create/gh pr merge— the run's deliver phase opens the PR; standalone, the human does. Leave the files on the working tree.
Output
Assertion suite + a freshness / drift report. On failure, show the offending rows (bounded sample) and the invariant that broke.
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.
- 1mo ago Changed · -7 lines 318f7cacd602
- 1mo ago Changed · +18 lines 013737b40262
- 1mo ago First seen · 52 lines · 65 tokens per session scan A 83b9a797e41b
wicked-garden-qe-data-quality-tester is a skill published in the GitHub repository mikeparcewski/wicked-garden (9 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 567 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
pytest-databases
Auto-activate for pytestdatabases, Docker DB fixtures, PostgreSQL/pgvector/ParadeDB, MySQL/MariaDB, Oracle/SQL Server, CockroachDB, MongoDB, Redis/Valkey, BigQuery/Spanner, MinIO, or RustFS. Not for mocked DBs.
doctrine-fixtures-foundry
Build deterministic test data with zenstruck/foundry factories — Factory::createOne(), createMany(), states, sequences, lifecycle callbacks, lazy / eager flush, relation factories. Use with use Factories; + use ResetDatabase; (or DAMA Doctrine Test Bundle transaction rollback). Trigger when bootstrapping a test suite…
nemo-automodel-recipe-development
Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.
mcore-testing
Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.
i4h-catheter-navigation-e2e
End-to-end smoke for catheter navigation covering setup, digital twin, DRR, and unit tests. Use when asked to run the full catheter workflow smoke or demo the v0.7 pipeline.
test-gen
Generate and verify tests — happy path, edge cases, error paths — using the project's own framework and patterns.