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/urbanmorph/mdshare/mdshare-toolsnpx skills add urbanmorph/mdshare --skill mdshare-toolsgit clone --depth 1 https://github.com/urbanmorph/mdshareWhat 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.00104 | $0.00783 |
| Opus 5 | $0.00052 | $0.00392 |
| Sonnet 5 | $0.00021 | $0.00157 |
| Haiku 4.5 | $0.00010 | $0.00078 |
Grade A, and why
mdshare-tools 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mdshare — markdown sharing via MCP
mdshare is a free, no-login markdown sharing service at mdshare.live. This skill orchestrates 14 MCP tools that let Claude upload, read, edit, comment on, and version markdown documents.
When to use
- The user has a markdown file or just-generated markdown content they want to share
- The user wants link-based collaboration (comments, edit permissions, real-time sync)
- The user mentions mdshare specifically
When NOT to use
- The user wants Claude to read or edit local markdown files (use the standard file tools)
- The user wants to configure Claude with markdown context (CLAUDE.md / AGENTS.md territory — different concept)
- The content is sensitive — share links are the only auth; warn the user instead
Core conventions
- All arguments are literal strings. Shell substitution like
$(cat file)does NOT work. - For files on disk, prefer
file_path/output_path. Inline content over ~1KB burns tokens unnecessarily. keyis OPTIONAL on tools addressed bydocument_id— admin keys are looked up automatically from the local credential store.- Never surface admin URLs to the user unless they explicitly ask.
upload_markdownreturns onlyshare_urlby design. - For small edits, prefer
patch_documentoverupdate_document— keeps version history granular.
Tool reference
Sharing a new document
upload_markdown(file_path)— preferred; pass disk path so content never enters conversation contextupload_markdown(content)— fallback for inline content under ~1KB
Returns share_url. Admin URL is stored locally; surface only if explicitly asked via get_admin_url(document_id).
Editing an existing document
patch_document(document_id, operations)— preferred for small edits (find/replace operations)update_document(document_id, file_path)— for whole-doc rewrites; pass file_path not content
Generating links with specific permissions
generate_link(document_id, permission)—permissionis one ofadmin,edit,comment,viewrevoke_link(token)— invalidate a specific linklist_links(document_id)— see all active links
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.
- 3d ago First seen · 67 lines · 104 tokens per session scan A e0f170f95ed1
mdshare-tools is a skill published in the GitHub repository urbanmorph/mdshare (8 stars, last pushed 24d ago), licensed MIT. It adds 104 tokens to every session and 783 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…