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 JackVitick/socialync-mcp --skill social-queue-analyticsgit clone --depth 1 https://github.com/JackVitick/socialync-mcpWrote 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/jackvitick/socialync-mcp/social-queue-analytics)<a href="https://agentmods.dev/skills/jackvitick/socialync-mcp/social-queue-analytics"><img src="https://agentmods.dev/badge/skills/jackvitick/socialync-mcp/social-queue-analytics/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/jackvitick/socialync-mcp/social-queue-analytics"><img src="https://agentmods.dev/badge/skills/jackvitick/socialync-mcp/social-queue-analytics.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.00069 | $0.00591 |
| Opus 5.5 | $0.00028 | $0.00236 |
| Sonnet 5.5 | $0.00014 | $0.00118 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
social-queue-analytics 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 14d 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
Socialync queue and history
Reading needs no approval. Any change to the calendar follows the consent rule in the schedule-social-post skill: show exactly what will change and wait for a yes.
Start here
list_profilesto pick theprofileId.check_quotaif the question is about remaining posts or plan limits.
Read
- Upcoming and recently failed:
get_scheduled_posts. A failed post haserror.code, a plainmessageto relay, andaction. - Already published, or a check before any retry:
get_post_history. - A draft still waiting:
get_draft_status. - Performance numbers:
get_analyticsandget_top_posts(paid plans). For a full review, switch toweekly-what-worked.
Summarize as a table: local time, platforms, status, first line of text. Leave out raw JSON.
Change
- Cancel: show the post and ask. On a yes,
delete_scheduled_postwithgroupIdto cancel every platform of that post, orpostIdfor one platform. A published post cannot be removed. - Move to another time: there is no edit tool. Show the new time and ask. On a yes,
validate_postwith the newscheduledFor, thendelete_scheduled_post, thenpublish_scheduledwith the same content at the new time. For a video, confirm the clip still appears inlist_mediabefore you cancel, and reschedule straight away. - Publish early: for text or images, the same steps with
publish_nowin place ofpublish_scheduled. A video stays on the scheduled path. - Read back with
get_scheduled_postsafter every change.
Failures
action: "reconnect": tell the user which account to reconnect in Socialync Settings. You cannot fix a connection from here. Do not reschedule until they have reconnected.edit_post: show what needs to change, then follow the move steps with the fixed content.retryorwait_and_retry: offer a new time.- Before any retry, check
get_post_historyso you report what actually happened. Socialync blocks duplicate publishes.
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.
- 14d ago Changed · +3 lines · +21 tokens per session 17a4c27bdddf
- 1mo ago First seen · 39 lines · 48 tokens per session scan A 43ef4e7666b9
social-queue-analytics is a skill published in the GitHub repository JackVitick/socialync-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 591 once invoked, about $0.0003 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
platform-reference
Complete reference for all 15 BulkPublish platforms — post types, media requirements, required fields, character limits, and platformSpecific options. ALWAYS consult before creating posts.
schedule-post
Create, schedule, or publish social media posts via BulkPublish MCP. Use when the user wants to post to social media.
check-quota
Check BulkPublish plan limits and current usage. Use when the user asks about their plan, limits, or remaining quota.
get-analytics
Pull analytics, engagement metrics, and performance data from BulkPublish. Use when the user asks about post performance or engagement.
inbox-triage
Read, sort and answer the BulkPublish Inbox (direct messages, reviews and comment threads) with a confirmation before every reply. Use when the user asks about messages, DMs, reviews, what is waiting for a reply, or wants to clear, snooze, archive or assign conversations.
comment-replies
Read the comments on a published BulkPublish post and reply to, like, hide or delete them, with a confirmation before anything is posted or removed. Use when the user asks who commented on a post, wants to answer comments, or wants to clear spam from a post.