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 commands/rockyco/claude-x-plugin/postgit clone --depth 1 https://github.com/rockyco/claude-x-pluginWrote 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/commands/rockyco/claude-x-plugin/post)<a href="https://agentmods.dev/commands/rockyco/claude-x-plugin/post"><img src="https://agentmods.dev/badge/commands/rockyco/claude-x-plugin/post.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.00012 | $0.00880 |
| Opus 5 | $0.00006 | $0.00440 |
| Sonnet 5 | $0.00002 | $0.00176 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
X Post
Compose and publish content to X (Twitter). Supports text and image posts.
Step 1: Check authentication
Run this to verify credentials:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/x-api.py check-auth
If it fails, tell the user to run /x:setup first.
The token auto-refreshes, so "expired" status is usually fine - it will refresh on the next API call.
Step 2: Determine post type
Based on the user's request and any arguments provided, determine the post type:
- Text only: User provides just text content
- With images: User provides text + image file paths (1-4 images)
If the user's intent is unclear, use AskUserQuestion to clarify.
Step 3: Craft the content (ALWAYS, every time)
Load the x-api skill and apply its "Writing an attractive, readable post" and "Diagrams for
X posts" sections. Do this on EVERY post, not just the first.
Write the text for X. Never paste an article abstract or a post from another channel verbatim - re-cut the source into an X-native post: hook the first line (surprising stat / bold claim / question / value prop), one idea per line with blank-line breaks, keep it tight and scannable, 3 or fewer hashtags at the end, mirror the source's honest claim-framing.
Build X-native diagrams when the post carries images. Do not reuse carousel / article
slides as-is. Use the svg-diagram skill to produce an X-specific set: strip page numbers
(N / M) and swipe → prompts, keep headline numbers centered (X crops previews center-out),
use ONE consistent aspect ratio for all images, render PNGs with rsvg-convert -z 2 -b white,
and save them to their own dir (e.g. docs/x/<slug>/images/). Order them to read as a sequence.
Then review with the user before publishing:
- Show the full text that will be posted
- Note the character count (280 for free accounts, 25,000 for premium)
- List the images that will be uploaded (and confirm they are the X-native set, not the source slides)
- Ask for confirmation before publishing
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 · 94 lines · 12 tokens per session scan A 2f0d8e5a9238
post is a command published in the GitHub repository rockyco/claude-x-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 880 once invoked, about $0.0001 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 commands, from other repositories
x-post
Draft (or take) a tweet/thread, optionally attach an image, score it against a built-in bookmarkability rubric, preview the cost, and post to X — ONLY after you explicitly confirm. Never auto-publishes. Can also SCHEDULE for later via vibedraft (single posts may carry one image or mp4 video; bulk is text-only)…
post
Compose a LinkedIn post bundle (text + images / carousel) saved to a local directory for manual review and publishing.
comments
View and reply to comments on a LinkedIn post.
setup
Set up LinkedIn API authentication (OAuth 2.0).
status
Check LinkedIn authentication status and token health.
git
Git operations with intelligent commit messages and workflow optimization.