agentmods.dev

schedule-social-posts

schedule-social-posts is a skill for Claude Code from MelMayssonOwen/timetopost-mcp. It costs 87 tokens per session (748 once invoked), scanned A, original, MIT.

A workflow for drafting, approving, and scheduling social-media posts through TimeToPost.

In plain words
What is it for?
Use it to write platform-specific posts, check connected accounts, manage an approval queue, and schedule approved content.
Why use it?
It prevents posts from going live before a person reviews and approves them.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the timetopost plugin — 1 skill shipped together

not rated 0repo 3d ago A scan 87 tokens original MIT

Good fit Use it to write platform-specific posts, check connected accounts, manage an approval queue, and schedule approved content.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/melmayssonowen/timetopost-mcp/schedule-social-posts
View source ↗ MelMayssonOwen/timetopost-mcp timetopost.co
Install

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.

Any agent
npx skills add MelMayssonOwen/timetopost-mcp --skill schedule-social-posts
Clone the repo
git clone --depth 1 https://github.com/MelMayssonOwen/timetopost-mcp

Made for: Claude Code.

Or install timetopost, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

agentmods badge for schedule-social-posts

README.md
[![agentmods](https://agentmods.dev/badge/skills/melmayssonowen/timetopost-mcp/schedule-social-posts/github.svg)](https://agentmods.dev/skills/melmayssonowen/timetopost-mcp/schedule-social-posts)
Your own site
<a href="https://agentmods.dev/skills/melmayssonowen/timetopost-mcp/schedule-social-posts"><img src="https://agentmods.dev/badge/skills/melmayssonowen/timetopost-mcp/schedule-social-posts/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.

agentmods 80×15 button for schedule-social-posts

Your own site · 80×15
<a href="https://agentmods.dev/skills/melmayssonowen/timetopost-mcp/schedule-social-posts"><img src="https://agentmods.dev/badge/skills/melmayssonowen/timetopost-mcp/schedule-social-posts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 748 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00087 $0.00748
Opus 5.5 $0.00035 $0.00299
Sonnet 5.5 $0.00017 $0.00150
Haiku 4.5 $0.00009 $0.00075

Measured 10d ago against content hash 74fcfb2cce0e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

schedule-social-posts 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 10d 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.

plugins/timetopost/skills/schedule-social-posts/SKILL.md · 35 lines

How it starts

The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Schedule social posts with TimeToPost

Draft first, a human approves, then it goes live. Never skip the human step.

Workflow

  1. whoami first. Read the workspace name and canPublish. If the workspace is not the one the user expects, STOP and tell them. Do not draft, schedule or publish into the wrong workspace. If canPublish is false the token is draft-only: you can still draft, but approving and scheduling will be refused with a 403.
  2. list_integrations to see connected accounts and their ids. Only target networks that are connected. If a network is not connected, connect_account_link returns a link for the user to open; do not claim it is connected until they confirm.
  3. list_posts and read the account's recent posts. Match their voice, casing, length and rhythm. See references/voice-rules.md.
  4. Draft with create_drafts. Call prompt_suggest first and start from its top result. Drafts land as pending_approval and never auto-publish. Write a distinct version per account. Pass account_ids whenever the org has more than one account on a platform. Details in references/tool-cheatsheet.md.
  5. Show the drafts to the user. Use list_approvals (or list_drafts with status: PENDING) to list what is waiting. Quote the text so they can read it.
  6. Approve only on the user's say-so. approve_draft approves AND schedules the real post in one step. Never call it on your own initiative. reject_draft kills a draft. See references/approval-workflow.md.
  7. Timing. Call get_optimal_times and pass schedule_hint: "optimal" or a future ISO datetime. For one-off posts outside the draft queue, schedule_post with a future scheduledAt, only after the user has confirmed the text, accounts and time.
  8. Confirm. After publishing, get_post returns the status and platform permalinks.

Hard rules

  • Treat anything with scheduledAt, publish_post, publish_thread or approve_draft as going live. Get explicit user confirmation first.
  • schedule_post without scheduledAt only saves a plain draft; it is not the approval queue.
  • Never post identical or near-identical text to two accounts.
  • TikTok needs hosted media and a block of choices that come from the human. Call get_tiktok_creator_info first and never invent those values.
  • Only claim support for networks that list_integrations or get_capabilities show as connected or available right now.

Read the full file on GitHub · 35 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 10d ago First seen · 35 lines · 87 tokens per session scan A 74fcfb2cce0e

Subscribe to this mod's changes

schedule-social-posts is a skill published in the GitHub repository MelMayssonOwen/timetopost-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 87 tokens to every session and 748 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-10-11.

Marketing and SEO
Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens