Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/kostja94/openblognpx agentmods add skills/kostja94/openblog/integrate-product-siteWrote 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/integrate-product-site)<a href="https://agentmods.dev/skills/kostja94/openblog/integrate-product-site"><img src="https://agentmods.dev/badge/skills/kostja94/openblog/integrate-product-site/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/integrate-product-site"><img src="https://agentmods.dev/badge/skills/kostja94/openblog/integrate-product-site.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.00054 | $0.01102 |
| Opus 5.5 | $0.00022 | $0.00441 |
| Sonnet 5.5 | $0.00011 | $0.00220 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
integrate-product-site 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrate Product Site
OpenBlog is a blog module, not a full site builder. This skill wires the blog into an existing product domain so header/footer/logo match the main site.
This is the recommended default when the user mentions a product URL, marketing site, existing nav/footer, or “add blog to my site”.
Agent: confirm with the user
Before scaffolding, ask:
Do you already have a product site? If yes, start from INTEGRATION.md (subdirectory / subdomain / monorepo). Use
create-openblogonly for a greenfield demo.
If they have a site URL → proceed below. If greenfield only → hand off to setup-blog-module.
Start by reading INTEGRATION.md — it is the single entry point.
When to use
- User has a product site and wants
/blog, a subdomain, or monorepo merge - User needs navbar/footer/logo aligned with the main site
- User asks to run
npm run integrateor configurechrome.mode
Three layers (do not confuse)
| Layer | Where | You replace? |
|---|---|---|
| Site Chrome | templates/next/src/chrome/ |
Yes — match main site |
| Blog Chrome | packages/components + config |
Toggle via components.optional |
| Brand assets | public/brand/ or CDN in config |
Yes |
Reuse components from the product site first. If a required navbar, footer, breadcrumb, article layout, or other named component does not exist, use Bricks component-builder for construction guidance, then implement it in the target repository. Do not copy Bricks guidance into OpenBlog.
Choose integration pattern
| Pattern | URL example | Doc |
|---|---|---|
| Subdirectory (recommended) | yourproduct.com/blog/post |
integrations/patterns/subdirectory.md |
| Monorepo merge | Same deploy as main Next app | integrations/patterns/monorepo.md |
| Subdomain | blog.yourproduct.com/post |
integrations/patterns/subdomain.md |
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 Changed · +2 lines d0c93bab03fb
- 2mo ago First seen · 110 lines · 54 tokens per session scan A 5d817ea947f9
integrate-product-site is a skill published in the GitHub repository kostja94/openblog (7 stars, last pushed 4d ago), licensed MIT. It adds 54 tokens to every session and 1,102 once invoked, about $0.0002 per session on Opus 5.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
content-commerce
Turn your blog into a sales channel by embedding shoppable product cards in editorial content and tracking content-influenced revenue.
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…
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.
Blog Outline Generator
Generates a detailed, SEO-optimized blog post outline with H2/H3 structure, key points per section, and a hook.