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 sandraschi/bluesky-mcp --skill bluesky-outboxgit clone --depth 1 https://github.com/sandraschi/bluesky-mcpWrote 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/sandraschi/bluesky-mcp/bluesky-outbox)<a href="https://agentmods.dev/skills/sandraschi/bluesky-mcp/bluesky-outbox"><img src="https://agentmods.dev/badge/skills/sandraschi/bluesky-mcp/bluesky-outbox/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/sandraschi/bluesky-mcp/bluesky-outbox"><img src="https://agentmods.dev/badge/skills/sandraschi/bluesky-mcp/bluesky-outbox.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.00000 | $0.00168 |
| Opus 5 | $0.00000 | $0.00084 |
| Sonnet 5 | $0.00000 | $0.00034 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
bluesky-outbox 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 11d 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
Bluesky Outbox Skill
Role
Hold promotion drafts from fleet-public-relations-mcp until a human approves, then publish to Bluesky (dry-run by default).
Flow
- Fleet-PR:
pr_draft→pr_approve_draft→pr_queue_fediverse - This server: outbox
pending - Human: Outbox UI or
outbox_approve outbox_publish— posts only ifBLUESKY_DRY_RUN=0
Tools
bluesky_social_tool(operation=…)— outbox_* / timeline / notifications / accounts_listbluesky_help— ports and flow summary
Safety
Never auto-publish. Never bypass outbox for fleet drafts.
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.
- 11d ago First seen · 22 lines · 0 tokens per session scan A c7099f5c996d
bluesky-outbox is a skill published in the GitHub repository sandraschi/bluesky-mcp (0 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 168 tokens. 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.
Other skills, from other repositories
mastodon-outbox
Hold promotion drafts from fleet-public-relations-mcp until a human approves, then publish to Mastodon (dry-run by default).
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…