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/jackvitick/socialync-mcp/social-queue-analyticsnpx 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.svg" alt="Measured on agentmods" 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 | $0.00048 | $0.00413 |
| Opus 5 | $0.00024 | $0.00206 |
| Sonnet 5 | $0.00010 | $0.00083 |
| Haiku 4.5 | $0.00005 | $0.00041 |
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 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.
What it actually says
Socialync queue, history, and analytics
Read-only first. Mutations only when the user asks to change the calendar.
Always start here
list_profiles: pickprofileId.check_quotaif the question is about remaining posts or plan limits.
Calendar and history
- Upcoming:
get_scheduled_posts - Already shipped / duplicate check:
get_post_history - Draft still processing:
get_draft_status
Summarize in a table (time, platforms, status, title/first line). Do not dump raw JSON.
Analytics
get_analyticsfor follower and engagement by platform, with period-over-period change.get_top_postsbefore recommending what to make next. Pattern-match the next batch off real winners, not guesses.
Analytics and top posts are paid-plan features; on the free plan tell the user that plainly.
Changes
- Cancel a scheduled post:
delete_scheduled_postonly with explicit confirmation. - Publish a scheduled post early: not a separate tool. Confirm with the user, then
delete_scheduled_postandpublish_nowwith the same content (text and images only; video must stay scheduled). - Reschedule: confirm first, then
delete_scheduled_postandschedule_post_draft(orpublish_scheduledif they confirmed the exact content in chat) at the new time. Read back the calendar after.
Expired connections show up on list_connections. Tell the user to reconnect in Socialync settings. You cannot fix OAuth from here.
If a publish may have failed, get_post_history before any retry. Duplicate protection means a retry should not post twice, but history is the source of truth.
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 · 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 7d ago), licensed MIT. It adds 48 tokens to every session and 413 once invoked, about $0.0002 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…