cross-domain-reporting

cross-domain-reporting is a skill for Claude Code from mailgun/mailgun-plugins. It costs 22 tokens per session (365 once invoked), scanned A, original, Apache-2.0.

A reporting workflow for comparing email-sending domains in Mailgun, an email delivery service. It examines delivery, engagement, failures, complaints, unsubscribes, and domain health over consistent time periods.

In plain words
What is it for?
Use it to rank domains, investigate deliverability differences, compare brands or subaccounts, and identify infrastructure or sender-configuration issues.
Why use it?
It reduces misleading comparisons caused by different traffic types, send volumes, regions, IP setups, or authentication and DNS problems.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the mailgun-claude plugin — 15 skills, 7 commands, 1 MCP server shipped together

Good fit Use it to rank domains, investigate deliverability differences, compare brands or subaccounts, and identify infrastructure or sender-configuration issues.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mailgun/mailgun-plugins/cross-domain-reporting
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.

Any agent
npx skills add mailgun/mailgun-plugins --skill cross-domain-reporting
Clone the repo
git clone --depth 1 https://github.com/mailgun/mailgun-plugins

Made for: Claude Code.

Or install mailgun-claude, the plugin that ships this one along with the rest of its 15 skills, 7 commands, 1 MCP server.

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 cross-domain-reporting

README.md
[![agentmods](https://agentmods.dev/badge/skills/mailgun/mailgun-plugins/cross-domain-reporting.svg)](https://agentmods.dev/skills/mailgun/mailgun-plugins/cross-domain-reporting)
Your own site
<a href="https://agentmods.dev/skills/mailgun/mailgun-plugins/cross-domain-reporting"><img src="https://agentmods.dev/badge/skills/mailgun/mailgun-plugins/cross-domain-reporting.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 365 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00022 $0.00365
Opus 5 $0.00011 $0.00182
Sonnet 5 $0.00004 $0.00073
Haiku 4.5 $0.00002 $0.00036

Measured 8d ago against content hash 2db774c6e3e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

cross-domain-reporting 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.

plugins/mailgun-claude/skills/cross-domain-reporting/SKILL.md · 38 lines

What it actually says

Reporting Across Domains

Use this skill when the user asks to compare performance across Mailgun domains, brands, streams, or subaccounts.

Intake

Collect the domain list, region, date range, dimensions of interest, and whether the report should optimize for deliverability, engagement, infrastructure health, or executive summary.

Workflow

  1. Verify every requested domain is in the expected region.
  2. Query analytics metrics and logs using consistent filters and time windows.
  3. Compare delivery rate, failure rate, complaint rate, unsubscribe rate, open/click engagement, provider/device/country splits, and suppression impact when available.
  4. Flag domains with DNS, authentication, IP, warmup, or template differences that make the comparison unfair.
  5. Produce a short ranked summary and a deeper table of metrics.

Comparison Notes

  • Separate transactional, marketing, and platform tenant traffic when those streams use different domains, tags, or subaccounts.
  • Call out whether domains use shared IPs, dedicated IPs, or distinct IP pools.
  • Normalize by send volume so one large domain does not hide smaller domains with sharper risk signals.
  • Compare sender identity patterns when available, especially if many low volume senders are used under one domain.
  • State data gaps clearly when tracking, provider dimensions, or suppression data are missing.

Safety

Keep reporting in analysis mode unless the user asks for remediation. If remediation is requested, create a proposed action plan first and confirm each account change before using mutating tools.

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. 8d ago First seen · 38 lines · 22 tokens per session scan A 2db774c6e3e4

Subscribe to this mod's changes

cross-domain-reporting is a skill published in the GitHub repository mailgun/mailgun-plugins (1 stars, last pushed 18d ago), licensed Apache-2.0. It adds 22 tokens to every session and 365 once invoked, about $0.0001 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-31.

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

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens