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 divinevideo/divine-mobile --skill dead-cdn-dns-bypassgit clone --depth 1 https://github.com/divinevideo/divine-mobileWrote 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/divinevideo/divine-mobile/dead-cdn-dns-bypass)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/dead-cdn-dns-bypass"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/dead-cdn-dns-bypass/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/divinevideo/divine-mobile/dead-cdn-dns-bypass"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/dead-cdn-dns-bypass.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 Server-Side Request Forgery · line 81 Request target host is built from a dynamic or untrusted value. If the host is attacker-influenced, this enables SSRF to arbitrary internal or metadata endpoints.Fix: Do not build request URLs from untrusted input. Validate the host against an allowlist and reject internal/metadata addresses before issuing the request.
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.00117 | $0.01290 |
| Opus 5 | $0.00059 | $0.00645 |
| Sonnet 5 | $0.00023 | $0.00258 |
| Haiku 4.5 | $0.00012 | $0.00129 |
Grade A, and why
dead-cdn-dns-bypass 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 11d 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.
curl -sI \ How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dead CDN DNS Bypass - Recovering Content from Defunct Services
Problem
When a service shuts down, their DNS records stop resolving, making URLs appear completely dead. However, the actual content often still exists on CDN servers (Fastly, CloudFront, Akamai, etc.) that continue serving it - the servers just aren't reachable via normal DNS resolution.
Context / Trigger Conditions
- Service has shut down (Vine, defunct startups, etc.)
- Original CDN URLs return DNS resolution errors
- Content was hosted on a major CDN provider
- You need to recover/archive historical content
- Wayback Machine doesn't have the specific content
Solution
Step 1: Identify the CDN Provider
Look at the original URL hostname to identify the CDN:
*.cdn.vine.co→ Fastly*.cloudfront.net→ AWS CloudFront*.akamaized.net→ Akamai*.fastly.net→ Fastly
Step 2: Find CDN IP Addresses
For Fastly (common for many defunct services):
# Fastly's anycast IPs
151.101.1.6
151.101.65.6
151.101.129.6
151.101.193.6
For other CDNs, check their documentation or try known IP ranges.
Step 3: Test with Host Header
# Test if content is still served
curl -sI \
-H "Host: original-cdn-hostname.com" \
"http://FASTLY_IP/path/to/content"
# Example for Vine:
curl -sI \
-H "Host: mtc.cdn.vine.co" \
"http://151.101.1.6/r/videos/ABC123.mp4"
Step 4: Download Content
import requests
def download_via_cdn_ip(original_url: str, cdn_ip: str) -> bytes:
"""Download content bypassing dead DNS."""
import re
# Extract host and path from URL
match = re.match(r'https?://([^/]+)(/.+)', original_url)
if not match:
return None
host = match.group(1)
path = match.group(2)
# Hit IP directly with Host header
response = requests.get(
f"http://{cdn_ip}{path}",
headers={"Host": host},
timeout=30
)
if response.status_code == 200:
return response.content
return None
# Example usage
content = download_via_cdn_ip(
"http://mtc.cdn.vine.co/r/videos/ABC123.mp4",
"151.101.1.6"
)
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.
- 11d ago First seen · 161 lines · 117 tokens per session scan A 370e8afafe5d
dead-cdn-dns-bypass is a skill published in the GitHub repository divinevideo/divine-mobile (265 stars, last pushed today), licensed MPL-2.0. It adds 117 tokens to every session and 1,290 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
azure-messaging-webpubsub-java
Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.
google-safe-browsing
Prevent and fix Google Safe Browsing "Dangerous site" flags. Use when launching a public web app, buying/picking a domain, building a login or signup page, or when any site shows a red "Dangerous site" / "Deceptive site" warning in Chrome, Brave, Safari, Firefox, or Edge. Triggers on "dangerous site", "deceptive…