blog-engine

blog-engine is a skill for Codex from san-npm/skills-ws. It costs 82 tokens per session (6,639 once invoked), scanned A, original, MIT.

A complete workflow for researching, writing, and preparing one long-form blog article for search engines and AI answer tools. It covers the process from the initial brief through publishing checks and a later update.

In plain words
What is it for?
Use it to create or refresh a publish-ready article, including source research, reader-intent planning, headlines, internal links, JSON-LD, and on-page optimization.
Why use it?
It brings research, structure, writing, search optimization, links, structured data, and quality checks into one article process. This avoids managing those tasks separately.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to create or refresh a publish-ready article, including source research, reader-intent planning, headlines, internal links, JSON-LD, and on-page optimization.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/san-npm/skills-ws/blog-engine
Install

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.

Any agent
npx skills add san-npm/skills-ws --skill blog-engine
Clone the repo
git clone --depth 1 https://github.com/san-npm/skills-ws

Made for: Codex.

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.

agentmods badge for blog-engine

README.md
[![agentmods](https://agentmods.dev/badge/skills/san-npm/skills-ws/blog-engine/github.svg)](https://agentmods.dev/skills/san-npm/skills-ws/blog-engine)
Your own site
<a href="https://agentmods.dev/skills/san-npm/skills-ws/blog-engine"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/blog-engine/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.

agentmods 80×15 button for blog-engine

Your own site · 80×15
<a href="https://agentmods.dev/skills/san-npm/skills-ws/blog-engine"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/blog-engine.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,639 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00082 $0.06639
Opus 5.5 $0.00033 $0.02656
Sonnet 5.5 $0.00016 $0.01328
Haiku 4.5 $0.00008 $0.00664

Measured 2mo ago against content hash 907380a851e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

blog-engine 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 2mo 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.

skills/blog-engine/SKILL.md · 446 lines

How it starts

The opening of the file, as written. The whole thing — 446 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Blog Engine

Production pipeline for one excellent long-form post, from blank page to publish-ready and through its first refresh. This skill owns execution of a single article. It deliberately does not re-derive program strategy or engine internals — cross-link instead:

  • Topic clusters, editorial calendar, pillar/cluster model → content-strategy
  • Template/directory/comparison pages generated at scale → programmatic-seo
  • Engine-by-engine GEO stance, schema catalog, E-E-A-T, Core Web Vitals, hreflang → seo-geo
  • Headline/CTA frameworks (PAS/AIDA/4U/BAB), voice calibration, before/after rewrites → copywriting
  • Local intent (city/service pages, NAP, GBP) → local-seo
  • Post-publish distribution sequences → email-sequence, social-media-kit, social-media-growth

2026 ground rules (read first)

Search in mid-2026 is split between classic blue-link ranking and answer engines (Google AI Overviews & AI Mode, Bing Copilot, ChatGPT Search, Perplexity, Gemini, Claude). A post must work for both. Non-negotiables:

  1. Information gain over imitation. Copying the SERP's structure/word count produces derivative pages that Google's helpful-content systems and AI engines both ignore. Every post must add something the top results don't have: original data, a first-hand test, a named expert quote, a calculator, a decision table, or a clearer synthesis. Aim to be the source an answer engine quotes, not the tenth paraphrase.
  2. First-party experience (the extra "E"). Show you actually did the thing: screenshots you took, numbers you measured, a methodology paragraph, a dated byline with a real author bio and credentials. This is what separates a quotable post from spun content.
  3. Length follows intent, not a target. There is no minimum word count. A definition query deserves 600 focused words; a "best X for Y" comparison may need 3,000 with a table. Match the depth a satisfied reader needs and stop.
  4. Disclose AI assistance + keep an editorial gate. AI-drafted copy must be fact-checked, edited, and reviewed by a named human before publish. Add a transparency note in your content policy (e.g., "Drafted with AI assistance, reviewed and edited by [author]") where your jurisdiction or audience expects it. Mass-produced, unreviewed AI pages are the exact pattern Google's scaled-content-abuse policy (March 2024, enforced through 2026) demotes — see programmatic-seo for the scale-safe variant.
  5. Citation hygiene. Cite primary sources (the study, the docs, the filing — not a blog citing a blog). Record the publish/last-updated date of every source; drop or re-verify anything older than ~18 months for fast-moving topics. Never fabricate a statistic, quote, or study; if you can't verify it, cut it.

Read the full file on GitHub · 446 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 2mo ago First seen · 446 lines · 82 tokens per session scan A 907380a851e1

Subscribe to this mod's changes

blog-engine is a skill published in the GitHub repository san-npm/skills-ws (4 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 6,639 once invoked, about $0.0003 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.

Related

blog-engine compared with skills from other repositories

blog-engine next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
blog-enginesan-npm/skills-wsSkill41mo agoMITA82Codex
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code