Borrowing it
Nothing to install: this file belongs to luanmorenommaciel/agentspec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/luanmorenommaciel/agentspec/main/.claude/commands/data-engineering/data-contract.mdgit clone --depth 1 https://github.com/luanmorenommaciel/agentspecWrote 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/luanmorenommaciel/agentspec/data-contract)<a href="https://agentmods.dev/commands/luanmorenommaciel/agentspec/data-contract"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/data-contract/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/commands/luanmorenommaciel/agentspec/data-contract"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/data-contract.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.00020 | $0.00330 |
| Opus 5.5 | $0.00008 | $0.00132 |
| Sonnet 5.5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
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 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.
What it actually says
Data Contract Command
Author producer-consumer data contracts following the Open Data Contract Standard
Usage
/data-contract <description-or-file>
Examples
/data-contract "Contract between orders team and analytics"
/data-contract "SLA definition for customer dimension table"
/data-contract models/marts/mart_revenue.sql
/data-contract "Schema governance rules for the payments domain"
What This Command Does
- Invokes the data-contracts-engineer agent
- Analyzes your contract requirements or existing model
- Loads KB patterns from
data-qualityanddata-modelingdomains - Generates:
- ODCS-compliant contract YAML
- Schema definitions with column-level contracts
- SLA specifications (freshness, completeness, accuracy)
- Producer-consumer agreement documentation
- Breaking change detection rules
Agent Delegation
| Agent | Role |
|---|---|
data-contracts-engineer |
Primary — ODCS, SLAs, schema governance |
data-quality-analyst |
Escalation — quality rule enforcement |
schema-designer |
Escalation — schema evolution planning |
KB Domains Used
data-quality— SLA patterns, quality metrics, observabilitydata-modeling— schema evolution, compatibility rules
Output
The agent generates ODCS contract YAML, SLA definitions, and governance documentation.
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 First seen · 55 lines · 20 tokens per session scan A 49979cd979e4
data-contract is a command published in the GitHub repository luanmorenommaciel/agentspec (256 stars, last pushed 4d ago), licensed MIT. It adds 20 tokens to every session and 330 once invoked, about $0.0001 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-01.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
security
Scan a SQL string, .sql file, or SQL-building source file for injection risks with GoSQLX.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
new-migration
Scaffold a new database migration file pair (up + down) with auto-detection of migration tool and numbering.
json.batch_get
Read multiple JSON values by document and path.
json.batch_delete
Delete multiple JSON documents or paths in one itemwise batch.