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 azeemkafridi/bulkpublish-api --skill media-librarygit clone --depth 1 https://github.com/azeemkafridi/bulkpublish-apiWrote 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/azeemkafridi/bulkpublish-api/media-library)<a href="https://agentmods.dev/skills/azeemkafridi/bulkpublish-api/media-library"><img src="https://agentmods.dev/badge/skills/azeemkafridi/bulkpublish-api/media-library/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/azeemkafridi/bulkpublish-api/media-library"><img src="https://agentmods.dev/badge/skills/azeemkafridi/bulkpublish-api/media-library.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.00035 | $0.00435 |
| Opus 5.5 | $0.00014 | $0.00174 |
| Sonnet 5.5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
media-library 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 21d 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
BulkPublish — Media
Tools
| Tool | Use for | Key params |
|---|---|---|
upload_media |
Add a file from a URL or local path | url OR filePath, optional filename |
list_media |
Find existing files | search, type, page, limit |
view_media |
Browse the library visually | limit |
create_media_upload |
Reserve a direct upload (advanced) | contentType, sizeBytes |
finalize_media_upload |
Register that upload (advanced) | r2Key, fileName, mimeType, sizeBytes |
For anything ordinary, use upload_media. The two advanced tools exist for a
large direct upload and must be used as a pair — reserve, upload, then register.
A reservation that is never registered stores nothing.
Attaching to a post
upload_media returns the stored file. Pass its ID in mediaFileIds on
create_post. Upload first, then create the post — a post cannot reference a
file that does not exist yet.
Before uploading
- Supported: JPEG, PNG, WebP, GIF, MP4, MOV, WebM. Maximum 100MB.
- Provide either
urlorfilePath, never both. - Check the target platforms' requirements first with
media-preflight: dimensions, aspect ratio and duration limits differ per platform and per post type, and a file that is fine for one can be rejected by another.
Notes
list_mediareturns URLs and dimensions, so prefer it over re-uploading a file the user already has.- Deleting media is not available here; tell the user it is done in BulkPublish.
- Uploading the same file twice stores two copies.
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.
- 21d ago First seen · 42 lines · 35 tokens per session scan A fe9364218466
media-library is a skill published in the GitHub repository azeemkafridi/bulkpublish-api (3 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 435 once invoked, about $0.0001 per session on Opus 5.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-09-25.
Other skills, from other repositories
zernio
Schedule posts, manage inbox, broadcasts, sequences, and automations across 14 platforms from the CLI.
schedule-social-post
Draft, schedule or publish social media posts to Instagram, TikTok, YouTube, Facebook, X, LinkedIn, Threads and Bluesky through the hosted Socialync MCP server, with the user's approval on every post. Use when the user wants to post, cross-post, publish now, schedule one post or a batch, send a video to TikTok, Reels…
restaurant-social
30-day social media content calendar — daily content ideas across Instagram, TikTok, and Facebook with platform-specific formatting.
blog-to-a-week-of-posts
Turn one blog post, newsletter, transcript or long article into a week of LinkedIn and X posts (plus Threads and Bluesky if the user wants), each one standing on its own, scheduled through Socialync with the user's approval on every post. Use when the user shares a URL or pastes long-form text and asks to repurpose…
film-once-week-of-shorts
Turn one filming session into a week of short-form video on TikTok, Instagram Reels and YouTube Shorts, scheduled through Socialync with the user's approval on every post. Use when the user has batch-filmed several clips and wants them spread across the week, or says "schedule my videos for the week", "post one clip a…
weekly-what-worked
Run a weekly review of the user's social media from their Socialync analytics, showing which platform grew, which posts did best and worst and what they have in common, which posts failed, and where next week's calendar has gaps, then propose next week's posts. Use when the user asks what worked, how last week went…