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/kostja94/openblog/agents-mdgit clone --depth 1 https://github.com/kostja94/openblogWrote 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/kostja94/openblog/agents-md)<a href="https://agentmods.dev/instructions/kostja94/openblog/agents-md"><img src="https://agentmods.dev/badge/instructions/kostja94/openblog/agents-md.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 | $0.01769 | $0.01769 |
| Opus 5 | $0.00885 | $0.00885 |
| Sonnet 5 | $0.00354 | $0.00354 |
| Haiku 4.5 | $0.00177 | $0.00177 |
Grade A, and why
openblog AGENTS.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 3d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — OpenBlog
You are editing OpenBlog, an open-source, Git-based CMS for blogs — implemented as an agent-native blog module for product websites. Content lives in Git (Markdown + frontmatter); you maintain routes, theme, site chrome, and SEO primitives (sitemap, RSS, robots, JSON-LD) through the repo. For site-wide SEO, GEO, keyword strategy, and marketing-page optimization, use marketing-skills — OpenBlog only guarantees blog-path SEO primitives.
Existing product site? Read INTEGRATION.md before editing chrome.
Agent: route the user first
When someone opens this repo without a clear task, ask which path applies before editing files:
| User situation | Point them to | Skill |
|---|---|---|
Has a product / marketing site — wants /blog, matching nav/logo |
INTEGRATION.md | blog-cms → integrate-product-site |
| Greenfield — new blog, local demo, no existing site | Quick start → scaffold (create-openblog) |
blog-cms → setup-blog-module |
| Module already wired — add or edit a post | Content model in this file | create-post (optional) |
| Pre-merge / deploy checks on blog posts | Validate + build | validate-blog-seo |
| Ready to merge and deploy | Git → CI checklist | publish (optional) |
Suggested prompt to show the user:
OpenBlog has two common paths:
- Existing product site → integrate
/blogvia INTEGRATION.md (recommended)- Try it first →
npm run create-openblog -- my-blogornpx create-openblog(after npm publish)
Which applies to you? If you have a product site URL, share it.
Do not default to create-openblog if they mention an existing website, product URL, chrome, or navbar alignment.
Contributions: Upstream PRs to this repo are enterprise-only (design-token or component/platform partners). Do not encourage individual users to open PRs — point them to INTEGRATION.md, Issues, or CONTRIBUTING.md for enterprise partnership inquiries.
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.
- 3d ago First seen · 166 lines · 1,769 tokens per session scan A ad32f2bad797
openblog AGENTS.md is an instructions file published in the GitHub repository kostja94/openblog (4 stars, last pushed 5d ago), licensed MIT. It adds 1,769 tokens to every session, about $0.0088 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 instructions, from other repositories
repo-seed AGENTS.md
Instructions for EricSanchezok/repo-seed, covering agents.md, repository governance, repository layout, code readability and commands.
quireink CLAUDE.md
Claude Code instructions for joiha-steven/quireink, covering quire ink, verify, read first, debug router — a symptom, and the files to open first and hard rules — each one is a bug that already shipped.
basic-blog AGENTS.md
Instructions for daocodotorg/basic-blog, covering agent notes — basic-blog monorepo, scope, npm release (automatic when version changes), when to tag and commands (agent should run these unless the user opts out).
excalibur-blog-cloud-public AGENTS.md
AGENTS.md instructions for Horosheff/excalibur-blog-cloud-public, covering excalibur blog cloud instructions, главное правило, cloud task fallback, что считать ошибкой and handoff и fragments.
repo-seed CLAUDE.md
Instructions for EricSanchezok/repo-seed, a project described as: Seed agent-native, self-governing repos: AGENTS.md, MADR decision logs, deterministic gates & pre-commit hooks. Upgradeable — never overwrites your edits.
blog-tech-kit AGENTS.md
Instructions for agentii-ai/blog-tech-kit, covering agents.md, about spec kit and specify, general practices, adding new agent support and current supported agents.