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 manage-channelsgit 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/manage-channels)<a href="https://agentmods.dev/skills/azeemkafridi/bulkpublish-api/manage-channels"><img src="https://agentmods.dev/badge/skills/azeemkafridi/bulkpublish-api/manage-channels/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/manage-channels"><img src="https://agentmods.dev/badge/skills/azeemkafridi/bulkpublish-api/manage-channels.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.00032 | $0.00411 |
| Opus 5.5 | $0.00013 | $0.00164 |
| Sonnet 5.5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
manage-channels 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.
What it actually says
BulkPublish — Connected Channels
Tools
| Tool | Use for | Key params |
|---|---|---|
list_channels |
Connected accounts as data | active (default true) |
view_channels |
The same list as an interactive view | none |
Prefer view_channels when the user wants to look at their accounts, and
list_channels when you need the IDs to build a post.
What comes back
Each channel carries its ID, platform, account name and connection status. Use
the channel ID in create_post — never the account name.
The response also carries a capabilities object saying whether this caller may
create, publish or approve posts. Check it before attempting a write, rather
than discovering the limit from a 403.
Reconnecting
A channel can be connected but no longer usable, because the account's authorization expired or was revoked on the platform's side. Those channels are flagged in the response. A publish to one will fail, so surface it before scheduling: tell the user which account needs reconnecting and that it is done in BulkPublish under Channels. You cannot reconnect an account from here.
A LinkedIn channel is either a personal profile or a company page
(accountType: personal / organization). Both are posted to the same way,
but they are gated separately — one can be unavailable while the other works.
When that is what blocks a write, the 403 PLATFORM_DISABLED error names the
accountType.
Notes
active: falseincludes channels the user has switched off.- If the user has no channels, say so plainly and point them to connecting one in BulkPublish; do not invent channel IDs.
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 · -8 lines · +5 tokens per session 475d9d67156d
- 1mo ago First seen · 56 lines · 27 tokens per session scan A cb805d28df59
manage-channels is a skill published in the GitHub repository azeemkafridi/bulkpublish-api (3 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 411 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.