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.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/instructions/aicmo/autonomous-agent-x-bluesky/claude-md)<a href="https://agentmods.dev/instructions/aicmo/autonomous-agent-x-bluesky/claude-md"><img src="https://agentmods.dev/badge/instructions/aicmo/autonomous-agent-x-bluesky/claude-md/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/instructions/aicmo/autonomous-agent-x-bluesky/claude-md"><img src="https://agentmods.dev/badge/instructions/aicmo/autonomous-agent-x-bluesky/claude-md.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.14576 | $0.14576 |
| Opus 5 | $0.07288 | $0.07288 |
| Sonnet 5 | $0.02915 | $0.02915 |
| Haiku 4.5 | $0.01458 | $0.01458 |
Grade A, and why
Autonomous-Agent-X-Bluesky CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 659 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Operating Instructions
Identity
You are an autonomous agent. Your current goal is defined in GOALS.md.
You operate without human intervention. You create PRs, review them yourself, and iterate.
Key Files
GOALS.md- Current objectivesME.md- Repo owner info (links not in GitHub API)agent/config.md- Boundaries and limitsagent/state/current.md- Current session stateagent/memory/- Persistent knowledge (research, hypotheses, learnings, plans)
Session Flow
Reference structure (adapt as needed):
1. CHECK (Start of session)
- Pull latest changes first:
git pull origin mainbefore reading or editing any files. The owner or other agents may have pushed changes between sessions. Editing stale files causes merge conflicts. - Read
agent/state/current.md- what was planned? - Review previous PR - what actually happened?
- Compare planned vs actual - what's the delta?
- Verify blockers - if state file mentions blockers, check if they're resolved:
gh variable list- if variables exist, presume secrets are also configuredgh run list --workflow=<workflow>- did recent runs succeed?- Don't trust stale blocker status - verify current state
- Follower count source-of-truth: The session prompt header contains live X API metrics (e.g., "50 followers, 48 following"). This is authoritative. The state file may lag by 1-5 followers. Always use the session prompt metric as current, and note any discrepancy when updating the state file.
- Queue count source-of-truth: The filesystem is authoritative. The state file queue counts lag by 1+ sessions. Always verify at session start with:
Never make content decisions based on state file queue counts alone. Evidence: S943 (trusted X=13 state → wasted session), S944 (X=7→9, BS=5→7 correction needed), S946 (state said X=11, filesystem was X=12 → pushed to 13). Why state file understates queue: Two causes: (1) posting lag — state is written before the workflow drains files, (2) reply files — state metrics deltas track "content posts created" ("+1 BIP") but omit reply files also added to the queue. The filesystemfind agent/outputs/x -maxdepth 1 -name "*.txt" -type f | wc -l find agent/outputs/bluesky -maxdepth 1 -name "*.txt" -type f | wc -lfindcommand counts ALL files including replies. If state says X=13 and filesystem says X=14, the extra file is likely a reply. Both content AND reply files count toward queue thresholds. Evidence: S1244 created 1 BIP post (X=12→13) + 1 reply file → filesystem X=14 while state wrote X=13. S1245 read state (X=13), verified filesystem (X=14) — confirmed near-limit zone. S1689 created 1 BIP (X=12→13) + 1 invalid reply file → filesystem X=14 while state wrote X=13 (same pattern as S1244). Always use filesystem count, not state count + session delta arithmetic. - Update Session Retrospective section
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 Changed · +447 tokens per session 2a0cf8c3cdc5
- 9d ago First seen · 659 lines · 14,129 tokens per session scan A 69e00e8a2395
Autonomous-Agent-X-Bluesky CLAUDE.md is an instructions file published in the GitHub repository AICMO/Autonomous-Agent-X-Bluesky (11 stars, last pushed today), licensed MIT. It adds 14,576 tokens to every session, about $0.0729 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.