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 schedule-postgit 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/schedule-post)<a href="https://agentmods.dev/skills/azeemkafridi/bulkpublish-api/schedule-post"><img src="https://agentmods.dev/badge/skills/azeemkafridi/bulkpublish-api/schedule-post/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/schedule-post"><img src="https://agentmods.dev/badge/skills/azeemkafridi/bulkpublish-api/schedule-post.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.00028 | $0.02234 |
| Opus 5.5 | $0.00011 | $0.00894 |
| Sonnet 5.5 | $0.00006 | $0.00447 |
| Haiku 4.5 | $0.00003 | $0.00223 |
Grade A, and why
schedule-post 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 1mo 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BulkPublish — Post Creation Reference
create_post parameters
content (string, required) — post text
channels (array, required) — [{channelId: number, platform: string}]
Get these from list_channels first
status ("draft"|"scheduled") — default "draft"
scheduledAt (ISO 8601 string) — required when status is "scheduled"
timezone (string) — e.g. "America/New_York", "Asia/Karachi"
mediaFileIds (number[]) — IDs from upload_media
platformContent (object) — per-platform text: {"x": "Short", "linkedin": "Longer version"}
postTypeOverrides (object) — per-platform format: {"instagram": "reel", "facebook": "story"}
postFormat ("post"|"video"|"reel"|"story"|"carousel"|"thread") — "thread" requires threadParts
threadParts (array) — [{content: string, mediaFileIds?: number[]}], min 2 parts.
EVERY part is length-checked against every target platform,
not just the first — an over-long part 400s the whole request
platformSpecific (object) — per-platform options; see the
platform-reference skill. Auto-reply after
publishing goes here as the top-level key
"_firstComment", NOT a firstComment param:
{"_firstComment": "Link in bio!"}
Unsupported on discord, pinterest, tiktok,
gmb, tumblr and snapchat (recorded as failed;
the main post still publishes)
requestApproval (boolean) — default false; hold a scheduled post for team
approval (approvalStatus becomes "pending")
linkTrackingOverride (boolean|null) — default null; per-post override for
bulkpubli.sh link tracking. true shortens the
post's links and counts clicks, false posts
them as written, null inherits the org setting
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.
- 1mo ago Changed a5c2ff59e708
- 1mo ago Changed · -32 lines a95b280d0f65
- 1mo ago First seen · 193 lines · 28 tokens per session scan A e09115452b00
schedule-post is a skill published in the GitHub repository azeemkafridi/bulkpublish-api (3 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 2,234 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-08-31.
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…
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…
social-queue-analytics
Inspect and manage the Socialync calendar and post history. Use when the user asks what is scheduled, what already posted, why a post failed, or wants to cancel, move or publish early a scheduled Socialync post. For a weekly performance review or "what worked", use the weekly-what-worked skill.