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 skills/entropy-data/dataproduct-builder-dbt/entropy-data-teamsnpx skills add entropy-data/dataproduct-builder-dbt --skill entropy-data-teamsgit clone --depth 1 https://github.com/entropy-data/dataproduct-builder-dbtWrote 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/entropy-data/dataproduct-builder-dbt/entropy-data-teams)<a href="https://agentmods.dev/skills/entropy-data/dataproduct-builder-dbt/entropy-data-teams"><img src="https://agentmods.dev/badge/skills/entropy-data/dataproduct-builder-dbt/entropy-data-teams.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.00107 | $0.01388 |
| Opus 5 | $0.00053 | $0.00694 |
| Sonnet 5 | $0.00021 | $0.00278 |
| Haiku 4.5 | $0.00011 | $0.00139 |
Grade A, and why
entropy-data-teams 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 5d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
List Entropy Data teams
Print the teams configured in Entropy Data and — if invoked from another skill — return the chosen team so the caller can fill in TEAM_NAME (for ODPS) without re-prompting the user.
How to run this skill
${PLUGIN_ROOT}below refers to the root of this plugin — the directory that containsskills/. 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 thisSKILL.mdfile's directory (i.e. the grandparent ofskills/<this-skill>/).
Plan announcement (before Step 0)
Before running Step 0, print this plan to the user verbatim:
Running entropy-data-teams. I'll:
- Pre-checks: verify the
entropy-dataCLI is installed and a connection is configured.- Fetch all teams from Entropy Data (paginated).
- Apply any filter you mentioned (substring on id/name/description, or type/tag match).
- Show the team list as a Markdown table.
- If invoked as a sub-step by another skill, ask you to pick one and return both
team.idandteam.nameto the caller.
Then proceed.
Step 0 — Pre-checks
uv run --quiet entropy-data --versionsucceeds from the project root. If it fails, runuv syncand retry; if still missing, stop and surface the install line from the README. Useuv run entropy-data …for every CLI invocation in this skill.- A connection / API key is configured. If
uv run entropy-data connection listis empty, tell the user to runuv run entropy-data connection add ...first; do not try to authenticate on their behalf.
Step 1 — Fetch teams
Run:
entropy-data teams list -o json
The response is a JSON array. Each team has at least: id, name, type, description, members[], tags[], links{}, custom{}.
Pagination: teams list accepts --page <n> (0-indexed). If the response has the same length as the configured page size, fetch the next page and merge until you get a short or empty page. Keep the merged list as TEAMS.
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.
- 5d ago First seen · 103 lines · 107 tokens per session scan A f25d35753502
entropy-data-teams is a skill published in the GitHub repository entropy-data/dataproduct-builder-dbt (12 stars, last pushed 3mo ago), licensed MIT. It adds 107 tokens to every session and 1,388 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.
Other skills, from other repositories
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.