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 j4flmao/agent-skills --skill data-meshgit clone --depth 1 https://github.com/j4flmao/agent-skillsWrote 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/j4flmao/agent-skills/data-mesh)<a href="https://agentmods.dev/skills/j4flmao/agent-skills/data-mesh"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/data-mesh/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/j4flmao/agent-skills/data-mesh"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/data-mesh.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 152 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00116 | $0.05645 |
| Opus 5 | $0.00058 | $0.02823 |
| Sonnet 5 | $0.00023 | $0.01129 |
| Haiku 4.5 | $0.00012 | $0.00564 |
Grade A, and why
data-data-mesh 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 8d 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 — 524 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Data Mesh
Purpose
Design data mesh architecture with domain-owned data products, self-serve platform capabilities, and federated governance — enabling decentralized data ownership at scale.
Agent Protocol
Trigger
Exact user phrases: "data mesh", "data product", "domain ownership", "self-serve data platform", "federated governance", "data as a product", "compute plane", "data topology", "domain decomposition", "cross-domain data sharing".
Input Context
- Organizational domains and team topology
- Current data platform maturity
- Data sharing patterns and pain points
- Governance and compliance requirements
- Number of data producers and consumers
- Technology stack and cloud providers
Output Artifact
Data mesh architecture with domain boundaries, data product designs (input/output ports), platform capability map, cross-domain data sharing model, and federated governance framework.
Response Format
# Domain decomposition map
# Data product blueprint (ports, schema, SLA)
# Platform capability matrix
# Cross-domain sharing model
# Governance policies
No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick.
Completion Criteria
- Domain decomposition aligned with business capabilities
- Data product definition with input/output ports, schema, and SLA
- Self-serve platform capabilities mapped to infrastructure
- Cross-domain data sharing with discovery and access control
- Federated governance model with global + local policies
- Data mesh maturity assessment with improvement roadmap
Max Response Length
350 lines of configuration.
Workflow
Step 1: Decompose by Domain
| Domain | Business Capability | Data Products |
|---|---|---|
| Commerce | Order management, product catalog, cart | orders, products, carts |
| Finance | Revenue, billing, invoicing | revenue, invoices, payments |
| Marketing | Campaigns, attribution, leads | campaigns, attribution, leads |
| Operations | Inventory, fulfillment, logistics | inventory, shipments, suppliers |
| Customer | Profiles, segmentation, engagement | customer_360, segments, interactions |
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/data-mesh-federated-governance.md 14 KB
- references/data-mesh-infrastructure-platform.md 19 KB
- references/data-product-template.md 4.4 KB
- references/domain-decomposition-patterns.md 5.2 KB
- references/mesh-data-product-implementation.md 917 B
- references/mesh-data-product-lifecycle.md 3.1 KB
- references/mesh-federated-governance.md 4.5 KB
- references/mesh-governance-operating-model.md 976 B
- references/mesh-implementation.md 3.6 KB
- references/mesh-principles.md 4.1 KB
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.
- 8d ago First seen · 524 lines · 116 tokens per session scan A b2a0fe45a36e
data-data-mesh is a skill published in the GitHub repository j4flmao/agent-skills (23 stars, last pushed 6d ago), licensed MIT. It adds 116 tokens to every session and 5,645 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
senior-data-engineer
World-class data engineering skill for building scalable data pipelines, ETL/ELT systems, real-time streaming, and data infrastructure. Expertise in Python, SQL, Spark, Airflow, dbt, Kafka, Flink, Kinesis, and modern data stack. Includes data modeling, pipeline orchestration, data quality, streaming quality…
project-planning
Converts a specification into a phased, dependency-ordered implementation plan. Use after specification is complete and before execution begins.
tasklist
Maintain a project's canonical TASKS.md or an opted-in studio portfolio task register with permanent IDs, ownership, lifecycle dates, and source provenance. Use to list, add, update, complete, or cancel tasks, view tasks across registered projects, or import selected action items from project artifacts. Do not use for…
meeting-minutes
Turn a meeting transcript, notes, or conversation into collision-safe, source-linked minutes in meetings/YYYY-MM-DD-slug.md. Use for project meeting records, attendance, discussion, stated information, decisions, action candidates, and open questions. Saving minutes never changes PROJECT.md, decisions/, or TASKS.md…
project
Create or maintain an Architecture Studio project — initialize its record bundle, remember sourced facts, capture or supersede decisions, inspect project status, or migrate a 1.x PROJECT.md. Use when the user says “set up the project,” “remember this,” “we decided,” asks about project context, or runs /as:project.