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 skills add sonichi/sutando --skill x-twittergit clone --depth 1 https://github.com/sonichi/sutandoWrote 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/sonichi/sutando/x-twitter)<a href="https://agentmods.dev/skills/sonichi/sutando/x-twitter"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/x-twitter.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 17 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00031 | $0.01450 |
| Opus 5 | $0.00015 | $0.00725 |
| Sonnet 5 | $0.00006 | $0.00290 |
| Haiku 4.5 | $0.00003 | $0.00145 |
Grade A, and why
x-twitter 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 4d 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.
urllib, no `requests`/`requests_oauthlib` install. `post`, `mentions` and `timeline` need the How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
X (Twitter)
Post, search, read, and monitor X from the command line.
When to use
The user wants to post to / read from X (Twitter) — publish a tweet or thread, reply, search recent tweets, check mentions/timeline, or pull engagement on a known tweet id. Not for other social platforms.
Failure modes
- 403 / "not permitted" on post → the X API tier doesn't allow writes, or the app lacks Read+Write permission (regenerate the access token AFTER setting RW).
- 429 rate-limited → API v2 free tier has low write/read caps; back off and retry later, don't loop.
- 401 → a key in
.envis missing or stale. The skill uses five:X_API_KEY,X_API_SECRET,X_ACCESS_TOKEN,X_ACCESS_TOKEN_SECRET, andX_BEARER_TOKEN. Reads authenticate with the bearer token, so a 401 on search/mentions/timeline is most often a staleX_BEARER_TOKEN, not the OAuth pair. - Done = the command prints the new tweet id / the result rows; a post with no id back did not publish.
Usage
Posting — use the browser session (live method)
The OAuth1 API post path below is NOT wired on this fleet: posting needs 4 write keys (X_API_KEY/SECRET + X_ACCESS_TOKEN/SECRET) that are not in the vault. Posting is NOT credit-gated — it just needs those keys, which we don't have. Do not conclude "X is blocked." The working path is a signed-in Chrome-for-Testing browser session:
# Is the profile signed in? (headless, exit 0 = yes, 2 = no)
node skills/x-twitter/x-post-browser.mjs check
# Owner signs in once (headed GUI window; email/phone — Google/Apple OAuth stay blocked)
node skills/x-twitter/x-post-browser.mjs login
# Compose only, screenshot, DO NOT publish (always run this first)
node skills/x-twitter/x-post-browser.mjs post "Your tweet text" --dry-run
# Publish (only after owner OKs the dry-run)
node skills/x-twitter/x-post-browser.mjs post "Your tweet text"
- Profile:
<workspace>/data/x-browser-profile, resolved throughscripts/sutando-config.sh workspace(override with$X_BROWSER_PROFILE, declared in this skill'smanifest.json). Per-host, holds live session cookies, and never synced —data/is in the vaultexcludelist. A profile still sitting at the pre-#2133 location is used with a one-line notice until you move it, so upgrading does not cost you a fresh sign-in.$X_LOGIN_DONE_SENTINELand$X_LOGIN_TIMEOUT_ITERSare declared alongside it but are test/CI controls — there is no reason to set them by hand. Sign-in survives ONLY becausecheck/poststrip Playwright's--use-mock-keychainso cookies decrypt with the real login keychain — seememory/reference_x_browser_signin_oauth_blocked_use_email_phone.md. - Always
--dry-runfirst and confirm with the owner before publishing. Nothing posts without an explicit OK.
What ships with it
7 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.
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.
- 4d ago First seen · 124 lines · 31 tokens per session scan A 84b674f8c86b
x-twitter is a skill published in the GitHub repository sonichi/sutando (393 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,450 once invoked, about $0.0002 per session on Opus 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-09-03.
Other skills, from other repositories
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
schedule
Reminders, automations, and recurring page, dashboard, or status monitoring (cron, RRULE, or fire-at).
inbox-cleanup
Run a high-recall, multi-pass email inbox cleanup. Pattern-based subject queries catch 25x more archivable email than sender scans alone. Includes urgency triage, classification signals, and post-cleanup filter setup.
inbox-management
Ongoing Gmail inbox management via scheduled runs. Archives known noise, flags urgent items, drafts replies in-thread (never auto-sends), and catches stale follow-ups. Empty polls spend no model tokens. Starts in flag-only mode.
outlook
Manage Outlook email — drafting, sending, organizing, rules, vacation replies, and inbox analysis.
notifications
Send notifications through the unified notification router.