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.
/plugin marketplace add mayank-io/mstack/plugin install fetchWrote 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/mayank-io/mstack/x-post)<a href="https://agentmods.dev/skills/mayank-io/mstack/x-post"><img src="https://agentmods.dev/badge/skills/mayank-io/mstack/x-post/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.
<a href="https://agentmods.dev/skills/mayank-io/mstack/x-post"><img src="https://agentmods.dev/badge/skills/mayank-io/mstack/x-post.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00104 | $0.06000 |
| Opus 5.5 | $0.00042 | $0.02400 |
| Sonnet 5.5 | $0.00021 | $0.01200 |
| Haiku 4.5 | $0.00010 | $0.00600 |
Grade A, and why
x-post scanned grade A with 1 finding 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 19d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
5. Downloads up to 4 images per post with `curl`, at original resolution. How it starts
The opening of the file, as written. The whole thing — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Download X Post
Capture an X/Twitter post or thread — text, metrics, images — through the user's logged-in gstack browser, and write it to a Markdown note.
This skill owns no extraction code. The DOM logic is references/extraction.js; the orchestration is ${CLAUDE_PLUGIN_ROOT}/scripts/. Both are tested, and both are shared with the x-account bulk harvester. Do not re-implement either here — a second copy drifts from the tested one, and the drift surfaces as a capture that looks fine and is missing half the thread.
Browser — always gstack, never headless
Browser work goes through the gstack browser, which holds the user's logged-in sessions. A fresh Playwright instance is logged out: it silently returns login walls or truncated content that looks like a successful capture.
B="$HOME/.claude/skills/gstack/browse/dist/browse"
"$B" connect # run from the target directory — another cwd spawns a second
# daemon and kills the headed session
"$B" goto "<url>"
"$B" js '<expression>'
The daemon must be in headed mode. browse status reports either headed (attached to the user's real Chrome, carrying their logins) or launched (gstack's own Chromium on a fresh profile, logged into nothing). A launched daemon returns a login wall for every gated page, and a login wall reads as a short page rather than an error — nothing downstream will flag it. Verify the mode, and force a restart when it is wrong:
"$B" status # must report `mode: headed`
"$B" connect --force-restart # only when it does not — a launched daemon holds a
# fresh profile with no logins, so nothing is lost
The _browse.py adapter runs this check inside connect() and refuses to continue if it cannot reach headed. Both entry points below go through it, so the check is automatic; do the same by hand when driving $B directly.
Run $B outside the command sandbox. Claude Code's Bash sandbox blocks the connection to the daemon, and $B status then reports Headed server running (PID …) but not responding — which reads as a hung daemon but is not one. Verified 2026-09-30: the same PID reported healthy, headed when the identical command ran unsandboxed, before and after. Before force-restarting a "not responding" daemon, re-run status unsandboxed. Restarting a healthy headed daemon costs nothing in logins, but it hides the real cause and every later $B call fails the same way.
What ships with it
1 file 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.
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.
- 19d ago Changed c430a2b8d393
- 1mo ago Changed · +2 lines 8f020a4100b2
- 1mo ago Changed · -197 lines · +12 tokens per session 97b3c9163773
- 2mo ago First seen · 512 lines · 92 tokens per session scan A 44f6f7edc123
x-post is a skill published in the GitHub repository mayank-io/mstack (6 stars, last pushed 3d ago), licensed MIT. It adds 104 tokens to every session and 6,000 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.