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 skills/markerikson/opencode-config-example/fetch-twitternpx skills add markerikson/opencode-config-example --skill fetch-twittergit clone --depth 1 https://github.com/markerikson/opencode-config-exampleWhat 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.00034 | $0.00601 |
| Opus 5 | $0.00017 | $0.00300 |
| Sonnet 5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
fetch-twitter 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 2d 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
Fetch Twitter/X Content
Fetch tweet content using Twitter's syndication API (the same endpoint used for tweet embeds).
Quick Usage
bun ~/.config/opencode/skill/fetch-twitter/fetch-twitter.js <tweet_url_or_id>
Examples
# From full URL
bun ~/.config/opencode/skill/fetch-twitter/fetch-twitter.js https://x.com/shanselman/status/2006301298933604666
# From tweet ID only
bun ~/.config/opencode/skill/fetch-twitter/fetch-twitter.js 2006301298933604666
Output Format
{
"id": "2006301298933604666",
"url": "https://x.com/shanselman/status/2006301298933604666",
"author": {
"name": "Scott Hanselman",
"handle": "@shanselman",
"verified": true
},
"text": "Full tweet text...",
"created": "2025-12-31T09:47:59.000Z",
"favorites": 389,
"hasMedia": false,
"mediaType": null,
"quotedTweet": {
"author": "@davidfowl",
"text": "Quoted tweet text...",
"url": "https://x.com/davidfowl/status/..."
}
}
How It Works
Twitter's syndication API (cdn.syndication.twimg.com) is used for tweet embeds and doesn't require authentication. It requires a token calculated from the tweet ID:
function getToken(id) {
return ((Number(id) / 1e15) * Math.PI)
.toString(36)
.replace(/(0+|\.)/g, '');
}
The endpoint is: https://cdn.syndication.twimg.com/tweet-result?id={tweetId}&token={token}
Limitations
- May occasionally fail (retry if needed)
- Rate limits are undocumented
- Could break if Twitter changes the embed system
- Does not fetch full threads, only the specific tweet (plus quoted tweet if present)
When to Use
When processing Twitter URLs:
- Detect
x.comortwitter.comURLs - Run:
bun ~/.config/opencode/skill/fetch-twitter/fetch-twitter.js <url> - Parse the JSON output
- Use
text,author.name,author.handlefor the markdown entry - Note
hasMediaandmediaTypeif relevant - Include
quotedTweetcontext if present
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.
- 2d ago First seen · 83 lines · 34 tokens per session scan A 73dfdc95de86
fetch-twitter is a skill published in the GitHub repository markerikson/opencode-config-example (44 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 601 once invoked, about $0.0002 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-30.
Other skills, from other repositories
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…