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 sinch/sinch-plugins --skill sinch-mailgun-inspectgit clone --depth 1 https://github.com/sinch/sinch-pluginsWrote 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/sinch/sinch-plugins/sinch-mailgun-inspect)<a href="https://agentmods.dev/skills/sinch/sinch-plugins/sinch-mailgun-inspect"><img src="https://agentmods.dev/badge/skills/sinch/sinch-plugins/sinch-mailgun-inspect/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/sinch/sinch-plugins/sinch-mailgun-inspect"><img src="https://agentmods.dev/badge/skills/sinch/sinch-plugins/sinch-mailgun-inspect.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.00046 | $0.03681 |
| Opus 5.5 | $0.00018 | $0.01472 |
| Sonnet 5.5 | $0.00009 | $0.00736 |
| Haiku 4.5 | $0.00005 | $0.00368 |
Grade A, and why
sinch-mailgun-inspect scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. **Language** — any language, or curl. This API is REST-only; there is no SDK wrapper. This is a copy
91% identical to sinch-mailgun-inspect — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mailgun Inspect
Overview
Mailgun Inspect (by Sinch) is an email pre-send quality control API. Five capabilities:
| Capability | Base Path | Input |
|---|---|---|
| Accessibility | /v1/inspect/accessibility |
html + encoded |
| Link Validation | /v1/inspect/links |
links URL array (or /html-validate for HTML) |
| Image Validation | /v1/inspect/images |
links URL array (or /html-validate / /upload) |
| Code Analysis | /v1/inspect/analyze |
html (no encoded field) |
| Email Previews | /v1/preview/tests (V1) / /v2/preview/tests (V2) |
varies |
(Summary only — confirm exact names/encoding/enums against the authoritative API Reference (Markdown) doc before implementing.)
For full endpoint tables and request schemas, see references/api-endpoints.md.
Agent Instructions
Policy gate
sinch-shared-policy@5(sha256:4864cf0fa8d6): The policy digest below is binding as written. Before implementation or live execution, read the full shared Sinch policy once per conversation — skip it if this exact ID/version/fingerprint is already loaded; read it if the version is newer or the fingerprint differs. This skill's canonical operation routes live in its Agent Instructions and Links sections.
Sinch policy digest (binding):
- Load the shared policy once per conversation; skip duplicate copies bearing the same ID/version/fingerprint.
- Infer product, language, region, and environment from the request and workspace; ask one combined question only for true blockers. Prefer the official Sinch SDK unless the request or workspace decides otherwise or no official SDK covers the language or operation.
- Code-generation approval is not execution approval. Classify every operation (read-only / reversible / billable / destructive) and obtain explicit approval before billable or destructive calls.
- Tier B facts — endpoint paths, methods, field names, enums, limits, webhook payloads, signature algorithms, SDK signatures — require fetching the exact canonical document in the current session before use.
- Bundled scripts, references, and examples are Tier C: illustrations, never schema authority. Never promote example values to production defaults.
- If a route is unresolved or a canonical fetch fails, climb the resolution ladder in order — re-search already-fetched documents (raw, not summarized), consult https://developers.sinch.com/llms.txt, follow first-party links, retry once — before failing closed. Never pattern-guess a documentation URL; never substitute memory, search snippets, or bundled files.
- Keep an evidence ledger mapping each fetched source to the fields and claims it authorized.
- Bound all polling and retries (backoff, jitter, hard cap); check state before retrying billable or destructive operations; report a timeout as unknown, not failed.
- Report verification levels separately (lint → unit → mock contract → sandbox → live → end-to-end); an HTTP 2xx does not prove delivery. State the levels not performed.
- Load only the smallest skill set that owns the behavior; if a required skill is unavailable, name it and stop rather than improvising its instructions.
What ships with it
2 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.
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 · 228 lines · 46 tokens per session scan A 72f0861c0724
sinch-mailgun-inspect is a skill published in the GitHub repository sinch/sinch-plugins (6 stars, last pushed 11d ago), licensed Apache-2.0. It adds 46 tokens to every session and 3,681 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 91% identical to sinch-mailgun-inspect, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
round-verification
Verify a CCB execution round and produce a machine-readable round result artifact.
node-check
Verify one CCB worker node and reject hidden fallback, degradation, scope shrinkage, or missing evidence.
team-lifecycle-v4
Full lifecycle team skill — plan, develop, test, review in one coordinated session. Role-based architecture with coordinator-driven beat model. Triggers on "team lifecycle v4".
team-testing
Unified team skill for testing team. Progressive test coverage through Generator-Critic loops, shared memory, and dynamic layer selection. Triggers on "team testing".
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.