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/microlinkhq/mcp/extract-media-sourcenpx skills add microlinkhq/mcp --skill extract-media-sourcegit clone --depth 1 https://github.com/microlinkhq/mcpWrote 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/microlinkhq/mcp/extract-media-source)<a href="https://agentmods.dev/skills/microlinkhq/mcp/extract-media-source"><img src="https://agentmods.dev/badge/skills/microlinkhq/mcp/extract-media-source.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 | $0.00102 | $0.00652 |
| Opus 5 | $0.00051 | $0.00326 |
| Sonnet 5 | $0.00020 | $0.00130 |
| Haiku 4.5 | $0.00010 | $0.00065 |
Grade A, and why
extract-media-source 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 4d 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.
What it actually says
Extract playable media sources
Resolve a page URL to a direct, playable media file URL.
Pick the tool
| Media | Tool | Result | Platforms |
|---|---|---|---|
| Video | microlink_video |
microlink.data.video.url |
YouTube, Vimeo, Twitter/X, TikTok, Instagram, Dailymotion, +hundreds |
| Audio | microlink_audio |
microlink.data.audio.url |
SoundCloud, Spotify, Mixcloud, + others |
Basic call — just pass the page URL:
{ "url": "https://www.youtube.com/watch?v=dQw4w9WgXcQ" }
Read the result
Video (microlink.data.video): url, type, duration, duration_pretty,
size, size_pretty, width, height.
Audio (microlink.data.audio): url, type, duration, duration_pretty,
size, size_pretty.
Confirm microlink.status === "success" and that data.video / data.audio is
present before using the source URL. If it's absent, the page has no detectable
playable media at that URL.
Options
meta: setfalseto skip page-metadata extraction and return only the media (faster, smaller). Or pass ametaobject to include specific fields.proxy(PRO): route through a proxy for platforms that geo-block or rate-limit — e.g.{ "url": "...", "proxy": "http://user:pass@host:port" }.force: true: bypass the cache and re-resolve the source.
Tips & gotchas
- The returned URL is a direct media link; it may be time-limited or signed by the source platform, so use it promptly rather than storing it long-term.
- Some platforms restrict access — if extraction fails on a public page, retry with a
proxy(PRO plan). - Only public URLs are supported; private/age-gated/login-walled media may not resolve.
- Respect the source platform's terms of service and copyright when reusing media.
- Free endpoint caps at 50 requests/day; set
MICROLINK_API_KEYfor more.
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.
- 4d ago First seen · 61 lines · 102 tokens per session scan A 3d5405bcef09
extract-media-source is a skill published in the GitHub repository microlinkhq/mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 652 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-31.
Other skills, from other repositories
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
post-to-xhs
小红书内容发布技能。支持两种发布模式:(1) 上传图文模式 - 图片+短文;(2) 写长文模式 - 长篇文章+排版模板。 支持两种输入方式:用户提供完整内容和图片/图片URL,直接发布;或提供网页URL,自动提取内容和图片。 用户说"发长文"时使用长文模式,否则默认图文模式。.
browser-video-recording
Create polished 60 fps 4:3 4K browser screen-recording style videos from Codex in-app browser captures, with browser-only crop, natural macOS cursor styling, deliberate click choreography, zoom-follow framing, ffprobe/thumbnail verification, and optional native recording compatibility checks. Use when the user asks to…
2-repro-issue
Reproduce a single LinkedIn-MCP issue locally on the current branch against the real authenticated LinkedIn session at /.linkedin-mcp/profile/, using the MCP streamable-http server. Captures the exact failure mode (tool output, error, missing data) and maps it back to the scraper code path. Use when the user says…