agentmods.dev

datacontract-edit

datacontract-edit is a skill for Claude Code, Codex from entropy-data/dataproduct-builder-dbt. It costs 108 tokens per session (1,958 once invoked), scanned A, original, MIT.

A tool for editing an output data contract: the specification describing the data a product promises to provide to its consumers. It tests the edited contract against live data and classifies failures as breaking or non-breaking.

In plain words
What is it for?
Use it to edit files under the output-port contract directory, run the contract test, inspect the diff, and get suggested fixes for failures.
Why use it?
It helps reveal whether a change will stop existing consumers from using the data. It also distinguishes changes to this product's contract from cached input contracts supplied by upstream products.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the dataproduct-builder-dbt plugin — 8 skills, 1 hook shipped together

not rated 12 3mo ago A scan 108 tokens original MIT
View the source file entropy-data/dataproduct-builder-dbt
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/entropy-data/dataproduct-builder-dbt/datacontract-edit
Any agent
npx skills add entropy-data/dataproduct-builder-dbt --skill datacontract-edit
Clone the repo
git clone --depth 1 https://github.com/entropy-data/dataproduct-builder-dbt

Made for: Claude Code, Codex.

Or install dataproduct-builder-dbt, the plugin that ships this one along with the rest of its 8 skills, 1 hook.

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 datacontract-edit

README.md
[![agentmods](https://agentmods.dev/badge/skills/entropy-data/dataproduct-builder-dbt/datacontract-edit.svg)](https://agentmods.dev/skills/entropy-data/dataproduct-builder-dbt/datacontract-edit)
Your own site
<a href="https://agentmods.dev/skills/entropy-data/dataproduct-builder-dbt/datacontract-edit"><img src="https://agentmods.dev/badge/skills/entropy-data/dataproduct-builder-dbt/datacontract-edit.svg" alt="Measured on agentmods" height="20"></a>
Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,958 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.00108 $0.01958
Opus 5 $0.00054 $0.00979
Sonnet 5 $0.00022 $0.00392
Haiku 4.5 $0.00011 $0.00196

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

Security

Grade A, and why

datacontract-edit 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 4d 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.

skills/datacontract-edit/SKILL.md · 119 lines

How it starts

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

Edit a data contract and test the impact

Change an output-port models/output_ports/v<N>/*.odcs.yaml file, run the contract test, and tell the user whether the change breaks consumers.

This skill operates only on output-port contracts — the spec this data product commits to. Input-port contracts under models/input_ports/ are cached snapshots of upstream's spec and are not editable here; if you want to refresh one (because upstream changed it), run dataproduct-implement instead.

How to run this skill

${PLUGIN_ROOT} below refers to the root of this plugin — the directory that contains skills/. On Claude Code it is set automatically as ${CLAUDE_PLUGIN_ROOT} — use that. On any other agent (Codex, Copilot CLI, etc.) it is unset; resolve it as ../.. relative to this SKILL.md file's directory (i.e. the grandparent of skills/<this-skill>/).

Plan announcement (before Step 0)

Before running Step 0, print this plan to the user verbatim:

Running datacontract-edit. I'll:

  1. Locate the output-port contract file under models/output_ports/v<N>/ that matches your request.
  2. Apply the edit in place and show you a unified diff.
  3. Run datacontract test against the live server to check the change.
  4. Classify each failure as breaking-schema, breaking-quality, additive, or unrelated.
  5. Report and suggest concrete fixes (no version bump, no v2 directory, no dbt model changes).

Then proceed.

Step 0 — Locate the contract

  • Search only models/output_ports/**/*.odcs.yaml — never models/input_ports/. If the user names an input-port contract, stop and explain it can't be edited here (refresh via dataproduct-implement instead).
  • If the user named a contract file or column, find the matching file under models/output_ports/.
  • If multiple contracts exist and it's ambiguous, list them and ask which one.
  • Read the file and remember the current models block as BEFORE.

Step 1 — Apply the edit

Edit the ODCS YAML in place using the user's instruction. Keep the change minimal — do not reformat unrelated fields.

Read the full file on GitHub · 119 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. 4d ago First seen · 119 lines · 108 tokens per session scan A f1e2a3592ccd

Subscribe to this mod's changes

datacontract-edit is a skill published in the GitHub repository entropy-data/dataproduct-builder-dbt (12 stars, last pushed 3mo ago), licensed MIT. It adds 108 tokens to every session and 1,958 once invoked, about $0.0005 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-30.

PlanningTestingdataproduct-builder
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

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 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