Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/setup-blog-module)<a href="https://agentmods.dev/skills/kostja94/openblog/setup-blog-module"><img src="https://agentmods.dev/badge/skills/kostja94/openblog/setup-blog-module.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.1 | $0.00056 | $0.00854 |
| Opus 5 | $0.00028 | $0.00427 |
| Sonnet 5 | $0.00011 | $0.00171 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
setup-blog-module 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Blog Module
Greenfield workflow for a new OpenBlog instance. Use when the user does not have an existing product site to integrate, or explicitly wants a local demo before INTEGRATION.
Agent: confirm with the user
If unclear, ask:
Do you want to mount
/blogon an existing product site (→ INTEGRATION.md), or run a local demo first (→create-openblog)?
Only use this skill after they choose greenfield / try-first.
When to use
- User wants a new blog from zero (standalone, subdirectory, or subdomain)
- User needs
openblog.config.ts, env, theme, orfeaturesconfigured - User asks to verify the project builds before first deploy
Steps
1. Scaffold
npx create-openblog my-blog
# or from monorepo root:
npm run create-openblog -- my-blog
Options: --dir <name>, --preset vercel-geist, --no-install. See packages/create-openblog/README.md.
2. Configure openblog.config.ts
At repo root, set:
site— name, description, locale,urlcontent— adapter and content dir (defaulttemplates/next/content/blog)theme— preset id or custom; runtheme:syncafter changesfeatures— toggle categories, tags, authors, RSS (seedocs/features.mdin monorepo, orFEATURES.mdin scaffolded projects)components.optional— Blog Chrome toggles (TOC, share bar, etc.)
3. Deploy environment
Copy templates/next/.env.example → .env.local:
SITE_URL=https://yourdomain.com
DEPLOY_MODE=subdirectory # subdirectory | subdomain | standalone
BLOG_BASE_PATH=/blog # subdirectory only
# ASSET_PREFIX=/blog # if static assets 404 behind reverse proxy
See templates/next/docs/DEPLOY-ROUTING.md for mode details.
4. Theme sync
npm run theme:sync # writes templates/next/src/app/theme.generated.css
dev and build run theme:sync automatically. See docs/theming.md. Optional: npm run theme:infer -- --url https://… for draft palette hints.
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 First seen · 99 lines · 56 tokens per session scan A e6abac2ea7f3
setup-blog-module is a skill published in the GitHub repository kostja94/openblog (4 stars, last pushed 7d ago), licensed MIT. It adds 56 tokens to every session and 854 once invoked, about $0.0003 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.