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 instructions/betterpost/betterpost-plugin/agents-mdgit clone --depth 1 https://github.com/betterpost/betterpost-pluginWhat 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 | $0.03630 | $0.03630 |
| Opus 5 | $0.01815 | $0.01815 |
| Sonnet 5 | $0.00726 | $0.00726 |
| Haiku 4.5 | $0.00363 | $0.00363 |
Grade C, and why
betterpost-plugin AGENTS.md scanned grade C with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`~/.codex/config.toml`: Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
A newly added server does not join the session that added it — clients read MCP configuration at startup, so `betterpost_*` tools stay absent until the client How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using BetterPost
BetterPost is a hosted service, available as an MCP server, that writes timely, well-sourced content. This guide covers what it does, how to add it, and how to use it — for both people and the agents acting on their behalf.
BetterPost writes timely, well-sourced content — newsletters, blog posts, LinkedIn posts, tweets, and Bluesky posts — grounded in current sources across news, social, and the open web. It finds recent sources relevant to a user's product and audience, ranks them by relevance, and writes human-sounding content with real citations and publication dates.
You reach BetterPost through its MCP server at https://betterpost.ai/mcp
(Streamable HTTP). Tools are namespaced betterpost_*. Sign in with your
BetterPost account when prompted — new accounts start with 100 free credits, and
there's no key to paste.
Add BetterPost
BetterPost is a remote MCP server, so any client that supports custom MCP connectors can use it — no install, no local process, no API key.
Already have the connector? If betterpost_* tools are listed in this session,
setup is done. Skip to "When to use BetterPost".
No betterpost_* tools? Then the connector isn't registered in this client yet,
and nothing else in this guide works until it is. Registration is a one-time config
change and it is the first step, not a fallback: an agent with shell or file access
registers the server itself, under whatever rules its client applies to configuration
changes. The one part that needs a person is the browser sign-in. Writing the user's
piece from model knowledge instead is not a substitute — see "If BetterPost isn't
connected" below for why.
1. Register the server
-
Claude Code —
--scope userregisters it for every project; the default scope islocal, which binds it to the current directory only.claude mcp add betterpost --scope user --transport http https://betterpost.ai/mcp
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.
- yesterday First seen · 216 lines · 3,630 tokens per session scan C 66d9d0dc14e7
betterpost-plugin AGENTS.md is an instructions file published in the GitHub repository betterpost/betterpost-plugin (0 stars, last pushed 20d ago), licensed MIT. It adds 3,630 tokens to every session, about $0.0181 per session on Opus 5. A static security scan graded it C with 2 findings (reads agent configuration directories, reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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.
buildNext
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain 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.