x-post

x-post is a command for Claude Code from rcmiskin10/x-poster. It costs 107 tokens per session (2,288 once invoked), scanned A, original, MIT.

A command for drafting, reviewing, scheduling, or publishing posts and threads on X, formerly Twitter. It can attach supported media and requires explicit confirmation before publishing or scheduling.

In plain words
What is it for?
Use it to turn text or an instruction into an X post, preview its cost and quality score, attach media, and publish or schedule it after confirmation.
Why use it?
It adds a review step and a bookmarkability score before an external post is sent, helping prevent accidental publication.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the x-poster plugin — 1 command, 1 hook, 1 MCP server shipped together

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add rcmiskin10/x-poster
Claude Code
/plugin install x-poster

Made for: Claude Code.

Or install x-poster, the plugin that ships this one along with the rest of its 1 command, 1 hook, 1 MCP server.

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 x-post

README.md
[![agentmods](https://agentmods.dev/badge/commands/rcmiskin10/x-poster/x-post.svg)](https://agentmods.dev/commands/rcmiskin10/x-poster/x-post)
Your own site
<a href="https://agentmods.dev/commands/rcmiskin10/x-poster/x-post"><img src="https://agentmods.dev/badge/commands/rcmiskin10/x-poster/x-post.svg" alt="Measured on agentmods" height="20"></a>
Per session 107 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,288 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00107 $0.02288
Opus 5 $0.00053 $0.01144
Sonnet 5 $0.00021 $0.00458
Haiku 4.5 $0.00011 $0.00229

Measured 5d ago against content hash 833c7aab12cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

x-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 5d 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/x-poster/commands/x-post.md · 115 lines

How it starts

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

/x-poster:x-post

Turn $ARGUMENTS into an X post via the x-poster MCP tools. Announce each step with its one-line emoji status so the user always knows where the workflow is.

HARD GATE — never auto-publish. Present the preview and get an explicit, affirmative confirmation ("ship it" / "ship it at 9am") in this conversation before calling publish_post or schedule_post. No bypass. The server's nonce/elicitation check is the backstop, not the gate.

Step 0 — route (decide deterministically, announce it)

  • $ARGUMENTS contains final text (quoted, or "post this …") → 📋 route: fast — verbatim text, skipping draft + rubric
  • $ARGUMENTS is an instruction ("draft a post about …") → 📋 route: draft
  • A future time is named (--at, "at 9am", "tomorrow", "schedule for …") → add 📅 mode: schedule to the route line. A scheduled post may carry ONE image (jpg/png/webp ≤ 5 MB) or mp4 video (≤ 512 MB) — pass image/video to schedule_post; the file uploads to vibedraft AFTER the gate, so a declined draft never spends an upload.
  • A LONG-FORM article is named ("post this as an article", "publish this .md as an X article", a markdown file over ~1,000 words) → 📰 route: article. This is a different format from a tweet or a thread: use preview_article then publish_article, NOT preview_post. Pass markdown_path for a file. publish_article creates a private draft unless the user explicitly says publish/go live — only then pass publish: true. Requires X Premium.
  • MULTIPLE independent posts with times ("draft 5 posts and schedule them across the week", "schedule these 10, one per morning") → 📅 mode: bulk-schedule (max 20 per batch). Bulk is TEXT-ONLY (items carrying media are rejected loudly — never silently drop media to make a batch work; say so and ask). Compute each post's concrete time yourself: resolve the user's spacing intent ("3/day at 9am/1pm/6pm starting tomorrow") to per-post ISO 8601 timestamps with the user's local UTC offset — the tools reject offset-less times. Keep items ≥30 min apart when posting order matters (vibedraft jitters each post ±a few min independently).

Read the full file on GitHub · 115 lines

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. 5d ago First seen · 115 lines · 107 tokens per session scan A 833c7aab12cd

Subscribe to this mod's changes

x-post is a command published in the GitHub repository rcmiskin10/x-poster (2 stars, last pushed 20d ago), licensed MIT. It adds 107 tokens to every session and 2,288 once invoked, about $0.0005 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.