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/sandraschi/bluesky-mcp/session-contextnpx skills add sandraschi/bluesky-mcp --skill session-contextgit 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/session-context)<a href="https://agentmods.dev/skills/sandraschi/bluesky-mcp/session-context"><img src="https://agentmods.dev/badge/skills/sandraschi/bluesky-mcp/session-context.svg" alt="Measured on agentmods" 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.00022 | $0.00142 |
| Opus 5 | $0.00011 | $0.00071 |
| Sonnet 5 | $0.00004 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
session-context 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 5d 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
Session Context (Bluesky MCP)
You can queue, approve, and publish Bluesky posts through a human-gated outbox.
Before starting work:
- Check pending drafts:
bluesky_social_tool(operation="outbox_list") - Review notifications:
bluesky_social_tool(operation="notifications")
At end of work:
- Enqueue drafts for human approval:
bluesky_social_tool(operation="outbox_enqueue", status_text="...") - Never publish directly without
outbox_approvefirst.
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.
- 5d ago First seen · 17 lines · 22 tokens per session scan A 0973eed0d193
session-context is a skill published in the GitHub repository sandraschi/bluesky-mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 22 tokens to every session and 142 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.
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).
code-style
PHP coding standards and WordPress patterns for ATmosphere plugin. Use when writing PHP code, creating classes, implementing WordPress hooks, or structuring plugin files.
test
Testing patterns for PHPUnit tests. Use when writing tests, debugging test failures, setting up test coverage, or implementing test patterns for ATmosphere features.
release
Version management and release processes using Jetpack Changelogger. Use when creating releases, managing changelogs, bumping versions, or preparing releases.
dev
Development workflows for WordPress ATmosphere plugin including wp-env setup, testing commands, linting, and build processes. Use when setting up development environment, running tests, checking code quality, or working with wp-env.
pr
INVOKE THIS SKILL before creating any PR to ensure compliance with branch naming, changelog requirements, and reviewer assignment.