Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add mayank-io/mstack/plugin install notesWrote 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/mayank-io/mstack/clip)<a href="https://agentmods.dev/skills/mayank-io/mstack/clip"><img src="https://agentmods.dev/badge/skills/mayank-io/mstack/clip/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/mayank-io/mstack/clip"><img src="https://agentmods.dev/badge/skills/mayank-io/mstack/clip.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.00088 | $0.04999 |
| Opus 5.5 | $0.00035 | $0.02000 |
| Sonnet 5.5 | $0.00018 | $0.01000 |
| Haiku 4.5 | $0.00009 | $0.00500 |
Grade A, and why
clip 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 2d 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.
| PDF (any host, incl. Drive/Dropbox) | `curl` → `notes:save-local-file` | — | How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clip
Route a URL to the correct extraction skill and note-writer. This skill is a router. It does not format notes and does not know vault conventions — the downstream skill owns that.
Input
The user provided: $ARGUMENTS — a URL, optionally followed by extra instructions (e.g. "tag it to project X", "capture with the edge-idea tag"). Pass extra instructions through to the downstream skill and honour them after it returns.
Step 1 — Identify the source
Match on the URL's host and path.
| Source | Fetch with | Template |
|---|---|---|
youtube.com, youtu.be |
fetch:youtube-download |
youtube.md (+ channel override) |
x.com, twitter.com |
fetch:x-post |
x.md |
linkedin.com |
fetch:linkedin-post |
linkedin.md |
*.notion.site, notion.so |
fetch:notion-public-site |
notion.md |
scribd.com |
fetch:scribd-document |
article.md |
alphaxiv.org, arxiv.org |
fetch:alphaxiv-paper |
paper.md |
pubmed.ncbi.nlm.nih.gov, ncbi.nlm.nih.gov/pmc |
fetch:pubmed-nlm |
paper.md |
instagram.com |
fetch:ig-post |
article.md |
| PDF (any host, incl. Drive/Dropbox) | curl → notes:save-local-file |
— |
| anything else | fetch:blog-post |
article.md |
The fallback goes to fetch:blog-post, not obsidian:defuddle. blog-post uses Defuddle internally and recovers the lazy-loaded images Defuddle drops, digitizes embedded Vedic charts via fetch:vedic-chart, and emits the same OUTPUT_DIR: contract as every other route. Routing straight to defuddle skips all of that and reaches outside this marketplace for a capability we already own.
Every route is the same six steps. There is no per-source skill, and there should never be one — what varies between sources is output shape, and shape lives in templates/.
Templates live at the plugin root — ${CLAUDE_PLUGIN_ROOT}/templates/ — not beside this skill. There is no skills/clip/templates/; a path resolved relative to this file finds nothing.
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.
- 2d ago Changed · +27 lines 402d3d2c79de
- 22d ago Changed · +2 lines de7d735d86c4
- 28d ago Changed · +7 lines 0dec1a581065
- 1mo ago Changed · +23 lines 80272446ae09
- 1mo ago Changed · +1 lines 1ee196ee7ce8
- 1mo ago Changed · +26 lines 079e5a659328
- 2mo ago First seen · 161 lines · 88 tokens per session scan A d7a98abc4038
clip is a skill published in the GitHub repository mayank-io/mstack (6 stars, last pushed 3d ago), licensed MIT. It adds 88 tokens to every session and 4,999 once invoked, about $0.0004 per session on Opus 5.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-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.