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 agentmods add commands/testingradial/r11-qdhenry-claude-command-suite-datascience/data-contractgit clone --depth 1 https://github.com/TestingRadial/r11-qdhenry-claude-command-suite-datascienceWrote 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/commands/testingradial/r11-qdhenry-claude-command-suite-datascience/data-contract)<a href="https://agentmods.dev/commands/testingradial/r11-qdhenry-claude-command-suite-datascience/data-contract"><img src="https://agentmods.dev/badge/commands/testingradial/r11-qdhenry-claude-command-suite-datascience/data-contract.svg" alt="Measured on agentmods" 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.00000 | $0.00783 |
| Opus 5 | $0.00000 | $0.00392 |
| Sonnet 5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
data-contract 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 6d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 6d ago First seen · 105 lines · 0 tokens per session scan A ac679e050f88
data-contract is a command published in the GitHub repository TestingRadial/r11-qdhenry-claude-command-suite-datascience (46 stars, last pushed 4mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 783 tokens. 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-30.
Other commands, from other repositories
ds-package
Package a model as a servable unit and prove prediction parity.
data-contract
You are a senior Data Science & AI/ML specialist. The user needs help with data contract in the context of data pipelines, model training, evaluation, mlops and analytical reporting.
ds-deploy
Serve a packaged model with monitoring, drift detection, and rollback.
ds-iterate
Diagnose what the evaluation found and route back to the stage that fixes it.
ds-baseline
Score a dumb baseline so the model has a number to beat.
ds-evaluate
Evaluate a model at an operating point, by slice, not one aggregate score.