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 skills add kostja94/openblog --skill blog-cmsgit 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/skills/kostja94/openblog/blog-cms)<a href="https://agentmods.dev/skills/kostja94/openblog/blog-cms"><img src="https://agentmods.dev/badge/skills/kostja94/openblog/blog-cms/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/kostja94/openblog/blog-cms"><img src="https://agentmods.dev/badge/skills/kostja94/openblog/blog-cms.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.00078 | $0.01490 |
| Opus 5 | $0.00039 | $0.00745 |
| Sonnet 5 | $0.00016 | $0.00298 |
| Haiku 4.5 | $0.00008 | $0.00149 |
Grade A, and why
blog-cms 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog CMS (OpenBlog)
OpenBlog is an open-source, Git-based CMS for blogs — an agent-native blog module mounted on product websites (typically /blog). Markdown in Git is the source of truth; Next.js renders list/post pages, RSS, sitemap, and JSON-LD.
Git is the CMS. Your coding agent is the admin.
This skill is the entry point. It routes to the right workflow, then reads the matching skill in this pack when present.
Not in scope: whole-site CMS, WordPress-style dashboards, site-wide SEO/GEO — pair with marketing-skills for growth workflows on the host site.
Install
# Entry skill only
npx skills add kostja94/openblog --skill blog-cms
# Recommended — entry + primary workflows
npx skills add kostja94/openblog --skill blog-cms integrate-product-site setup-blog-module
# Full pack (content ops included)
npx skills add kostja94/openblog --skill '*'
# List all skills in the repo
npx skills add kostja94/openblog --list
Repo: github.com/kostja94/openblog · Docs: INTEGRATION.md
When working inside the OpenBlog monorepo, read AGENTS.md and skill files under skills/ directly.
Step 1 — Route the user
Ask before editing files if the path is unclear:
OpenBlog has two common paths:
- Existing product site → integrate
/blogvia INTEGRATION.md (recommended)- Try it first →
npx create-openblog my-blog
Which applies to you? If you have a product site URL, share it.
| User situation | Action | Follow-up skill |
|---|---|---|
Existing product / marketing site — wants /blog, matching nav/logo |
Read INTEGRATION.md first | integrate-product-site |
| Greenfield — no site yet, local demo | Scaffold with create-openblog |
setup-blog-module |
| Module already wired — add or edit a post | Content model + validate | create-post |
| Pre-merge / deploy checks on blog posts | Validate + build | validate-blog-seo |
| Ready to merge and deploy | Git → CI checklist | publish |
| Ready to merge and deploy | Git → CI → CDN checklist | publish |
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 · 153 lines · 78 tokens per session scan A 8079316fba44
blog-cms is a skill published in the GitHub repository kostja94/openblog (6 stars, last pushed 11d ago), licensed MIT. It adds 78 tokens to every session and 1,490 once invoked, about $0.0004 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
repo-seed
Seed, audit, adopt, and progressively evolve an agent-native repository with risk-triggered specs, durable decisions, resident governance skills, capability state, deterministic gates, and safe upgrades. Use when initializing or upgrading a repository, when an unmanaged repository grows complex, or when delivery…
Blog Outline Generator
Generates a detailed, SEO-optimized blog post outline with H2/H3 structure, key points per section, and a hook.
Technical Blog Post Writer
Writes engaging, accurate technical blog posts targeted at developer audiences.
repo-review
Use when reviewing a pull request or a change in this repository — orients the reviewer to this repository's standards (AGENTS.md conventions, decision log, gates) and the review-specific checks that code alone cannot show.
repo-decisions
Use when a change chooses among meaningful alternatives whose rationale may be revisited, or when writing, updating, reviewing, or superseding a MADR record.
repo-governance
Use when repository complexity, delivery, ownership, security, release, or incident signals change; when governance may be missing; or when adding, reviewing, deferring, or upgrading repo-seed capabilities.