bsky-thread

A command that divides text into a Bluesky thread, where each post can contain up to 300 characters.

In plain words
What is it for?
Preparing long text for Bluesky by splitting it into numbered, readable posts.
Why use it?
It avoids awkward cuts by preferring paragraph, sentence, clause, and then word boundaries.

Command

Install

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.

agentmods
npx agentmods add commands/lhohan/claude-code-plugins/bsky-thread
Clone the repo
git clone --depth 1 https://github.com/lhohan/claude-code-plugins
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 678 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00678
Opus 5 $0.00006 $0.00339
Sonnet 5 $0.00002 $0.00136
Haiku 4.5 $0.00001 $0.00068

Measured yesterday against content hash f6bcefef8983, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bsky-thread 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 yesterday.

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.

hanlho-cmds/commands/bsky-thread.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are tasked with splitting text into Bluesky-compatible thread messages. Bluesky has a 300 character limit per post.

The user input below is either a file path or raw text:

{{prompt}}

Task Instructions

  1. Detect Input Type:

    • If input starts with @, it's a Claude Code file reference - convert to absolute path and read it
    • Check if the input is a file path (absolute paths or paths ending with common extensions like .txt, .md, etc.)
    • If it looks like a file path, use the Read tool to load the file content
    • If a file path is provided but doesn't have an extension (like LICENSE), still try to read it as a file
    • Otherwise, treat the entire input as the text to split
  2. Split Algorithm:

    • Target: 300 characters per message (use ~280-290 character soft limit to leave room for thread numbering like "[1/5] ")
    • Split at natural boundaries in this order of preference:
      1. Paragraph breaks (empty lines)
      2. Sentence endings (periods, question marks, exclamation marks)
      3. Clause boundaries (commas, semicolons)
      4. Word boundaries (last resort)
    • Never split mid-word or mid-sentence unless absolutely necessary
    • Preserve leading/trailing whitespace handling for readability
  3. Output Format:

    • Start with a header showing total message count: =� This will create X messages for your Bluesky thread:
    • Separate each message clearly with a visual divider
    • For each message, show:
      • Message label: [N/TOTAL]
      • Character count: (NNN chars) - count includes the "[N/TOTAL] " prefix
      • The actual message text with the [N/TOTAL] prefix included
    • Include empty lines between messages for readability
  4. Suggested Improvements (only if improvements are actually applicable):

    • After all messages, add a "=� Suggested improvements:" section
    • Suggest alternative thread break points that improve narrative flow or pacing
    • Propose minor clarity edits that maintain tone and content (grammar, awkward phrasing, etc.)
    • Format: - [Message N] Suggestion here or - [Overall] Suggestion here
    • Only include suggestions that genuinely improve the content

Read the full file on GitHub · 63 lines

Changes

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.

  1. yesterday First seen · 63 lines · 12 tokens per session scan A f6bcefef8983

Subscribe to this mod's changes

bsky-thread is a command published in the GitHub repository lhohan/claude-code-plugins (2 stars, last pushed 9mo ago), licensed MIT. It adds 12 tokens to every session and 678 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.