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/statusgit 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/status)<a href="https://agentmods.dev/commands/rockyco/claude-x-plugin/status"><img src="https://agentmods.dev/badge/commands/rockyco/claude-x-plugin/status.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.00166 |
| Opus 5 | $0.00006 | $0.00083 |
| Sonnet 5 | $0.00002 | $0.00033 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
status 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
X Status
Check the current X authentication status.
Action
Run the auth check:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/x-api.py check-auth
Also read ~/.claude/x.local.md for the full settings.
Report to user
Tell the user:
- Whether they are authenticated
- Their display name and @username
- Token status (minutes until expiration, or "expired - will auto-refresh")
- Whether a refresh token is present
- If the refresh token is missing, tell them to run
/x:setupto re-authenticate
Do NOT display the access_token or client_secret values.
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 · 32 lines · 12 tokens per session scan A 340a98b243b6
status 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 166 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.
init
Install the formatters this repository needs, with every command visible before it runs.