Let your agent run LinkedIn & X for you
$ social linkedin sql "SELECT sender_name, text FROM li_messages ORDER BY created_at DESC LIMIT 20"$ social x sql "SELECT sender_username, text FROM x_messages ORDER BY created_at DESC LIMIT 20"Paste the install prompt into Claude or Codex—no terminal required. Prefer the shell? The terminal installer is still available.
Accounts — social account connect linkedin · social account reconnect linkedin <account> · social account disconnect linkedin <account> · social account billing · social account. Connect, re-auth, inspect billing, and list the accounts on this network.
Accounts — social account connect x · social account reconnect x <account> · social account disconnect x <account> · social account billing · social account. Connect, re-auth, inspect billing, and list the accounts on this network.
jq, fzf, your agent's planner — anything that reads stdin.--limit bounds pages, LinkedIn list reads use --offset, and offset responses can expose .meta.totalCount. Cursor-based reads use --cursor and .meta.cursor; cacheable reads also take -H "Cache-Control: no-cache" for fresh upstream reads.$0.SKILL.md you drop straight into Claude, Codex, or any other agent.Agents tend to ask the same read questions while exploring. social has two read layers: live proxy reads, where selected repeats can hit cache, and the local mirror, where synced data can be queried for free with SQL.
sync pulls your own data into the local mirror and can spend usage. sql queries that mirror read-only, returns the standard envelope, and omits meta.cost.social account config cache ttl {total_in_seconds}.-H "Cache-Control: no-cache" on cacheable read commands when freshness matters. It skips the cached read and refreshes the stored response after a successful upstream call.no-store bypasses cache read and write; max-age=<seconds> overrides the TTL for one request.ETag and Last-Modified. The request cache surface is still Cache-Control; use no-cache for a fresh upstream read.meta.cache.tables, including last sync time and age.Cache-Control: no-cache, no-store, or max-age=<seconds> when the command lists --header.read,write. Clear Write in the prompt for a session that can't post, invite, or follow.$0. Audit it any time with social account billing, social account usage, and social account logs — nothing happens on your accounts you can't see.Built by @CyrusNewDay because it's a tool he needed.