Borrowing it
Nothing to install: this file belongs to AICMO/Autonomous-Agent-X-Bluesky. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AICMO/Autonomous-Agent-X-Bluesky/main/.claude/skills/publishing/SKILL.mdgit clone --depth 1 https://github.com/AICMO/Autonomous-Agent-X-BlueskyWrote 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/aicmo/autonomous-agent-x-bluesky/publishing)<a href="https://agentmods.dev/skills/aicmo/autonomous-agent-x-bluesky/publishing"><img src="https://agentmods.dev/badge/skills/aicmo/autonomous-agent-x-bluesky/publishing/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/aicmo/autonomous-agent-x-bluesky/publishing"><img src="https://agentmods.dev/badge/skills/aicmo/autonomous-agent-x-bluesky/publishing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 158 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 272 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Agent Snooping · line 492 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00024 | $0.18152 |
| Opus 5 | $0.00012 | $0.09076 |
| Sonnet 5 | $0.00005 | $0.03630 |
| Haiku 4.5 | $0.00002 | $0.01815 |
Grade A, and why
publishing 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publishing Content Strategy
Core principles for creating content that grows audience
Platform Status
Check current platform status (Premium tier, features, limits) in the integration plan files:
- X:
agent/integrations/x/plan.md - Bluesky:
agent/integrations/bluesky/plan.md
If plan files don't exist, create them from current state.
Expertise Pillars (Content Filter)
Every post MUST connect to at least one pillar. If it doesn't, skip it.
How Pillars Work
Pillars are the account's content lanes — topics where the owner has real authority. They are discovered, not hardcoded.
Where pillars come from:
- ME.md — Owner's background, expertise areas, current projects
- GOALS.md — What the account is trying to achieve
- This repo's purpose — What the agent actually does (autonomous content automation)
- What's working — Topics that get engagement (check metrics during retros)
Pillar lifecycle:
- Discover pillars at session start by reading ME.md and GOALS.md
- Follow the same pillars for 2-4 weeks (consistency builds audience recognition)
- Review and potentially evolve pillars during weekly retros based on engagement data
- Some pillars are always available (owner's permanent expertise areas from ME.md) but the agent can explore new ones
Current pillars are stored in agent/memory/pillars.md. If that file doesn't exist, discover pillars from ME.md and GOALS.md and create it.
AI Industry news is allowed ONLY as a hook to reach a pillar. The news is never the point. The connection to our expertise is.
Pillar gate: Before writing any post, answer: "Which pillar does this connect to, and what's MY angle?" If you can't answer both, skip.
What Actually Works (Evidence-Based)
Content formats ranked by performance (our data):
- News hooks — 3-6x average impressions (65, 62, 60, 51 imp vs 10 avg)
- Dollar-amount headlines — ($285B, $2B, $1T) quantified impact stops scroll
- Name-drops — (Karpathy, Altman, Anthropic, OpenAI) moderate boost
- Replies to official accounts — (@OpenAI 24 imp) > individuals (0-6 imp)
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.
- 9d ago First seen · 496 lines · 24 tokens per session scan A f0594d8ebf07
publishing is a skill published in the GitHub repository AICMO/Autonomous-Agent-X-Bluesky (11 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 18,152 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…