blog-post

blog-post is a skill for Claude Code, Codex from onfire7777/universal-ai-skills-library. It costs 57 tokens per session (753 once invoked), scanned A, a copy of blog-post, MIT.

A writing guide for producing a complete long-form article or blog page with a headline, author details, body sections, figures, quotes, and related posts.

In plain words
What is it for?
It is used for blog posts, essays, case studies, and other editorial pages of at least several sections.
Why use it?
It gives an article a consistent structure so the writer does not have to plan every page element from scratch.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is used for blog posts, essays, case studies, and other editorial pages of at least several sections.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/onfire7777/universal-ai-skills-library/blog-post
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 onfire7777/universal-ai-skills-library --skill blog-post
Clone the repo
git clone --depth 1 https://github.com/onfire7777/universal-ai-skills-library

Made for: Claude Code, 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-post

README.md
[![agentmods](https://agentmods.dev/badge/skills/onfire7777/universal-ai-skills-library/blog-post/github.svg)](https://agentmods.dev/skills/onfire7777/universal-ai-skills-library/blog-post)
Your own site
<a href="https://agentmods.dev/skills/onfire7777/universal-ai-skills-library/blog-post"><img src="https://agentmods.dev/badge/skills/onfire7777/universal-ai-skills-library/blog-post/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-post

Your own site · 80×15
<a href="https://agentmods.dev/skills/onfire7777/universal-ai-skills-library/blog-post"><img src="https://agentmods.dev/badge/skills/onfire7777/universal-ai-skills-library/blog-post.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 753 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 97% copy Near-identical to another mod 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.00057 $0.00753
Opus 5 $0.00028 $0.00377
Sonnet 5 $0.00011 $0.00151
Haiku 4.5 $0.00006 $0.00075

Measured 7d ago against content hash a7ca4747d9f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

blog-post 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 7d 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.

Origin

This is a copy

97% identical to blog-post — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/blog-post/SKILL.md · 82 lines

How it starts

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

Blog Post Skill

Produce a single long-form article page — editorial layout, no chrome.

Workflow

  1. Read the active DESIGN.md (injected above). Lean into the typography tokens — long-form is 70% type, 20% image, 10% chrome.
  2. Pick the topic from the brief and write a real article — at least 600 words across 4–6 H2 sections. No lorem ipsum.
  3. Sections, in order:
    • Masthead — small wordmark + 4–6 nav links, plain.
    • Article header — category eyebrow, headline (display token, large), deck (1–2 sentence subhead), author name + role + date.
    • Hero image — a 16:9 placeholder block using a DS-tinted gradient or solid fill (no external images). Add a 1-line caption underneath.
    • Body — alternating prose paragraphs with at least:
      • 1 pull quote (large display type, accent rule on the inline-start edge so the layout flips correctly under dir="rtl").
      • 1 figure (image placeholder + caption).
      • 1 list (numbered or bulleted).
      • 1 inline blockquote.
    • Author footer — author avatar (initials in a circle), bio paragraph.
    • Related — 3 cards linking to other posts. Each card: tiny image block, title, 1-line excerpt, date.
  4. Write a single HTML document:
    • <!doctype html> through </html>, CSS inline.
    • Article body uses the DS body font, centered, max-width per DS layout rule (typically 680–720px).
    • Drop caps (first-letter) only if the DS mood is editorial / serif — skip on tech-y DSes.
    • data-od-id on the headline, hero, body, pull quote, related grid.
  5. Self-check:
    • Type hierarchy is unambiguous — H1 is clearly the headline; H2s are section dividers; pull quotes do not compete with H1.
    • Line length 60–75 chars for body prose.
    • Accent appears at most twice (eyebrow + pull-quote rule, or one link).
    • The page reads like a magazine, not a marketing landing.

Output contract

Emit between <artifact> tags:

<artifact identifier="post-slug" type="text/html" title="Article Title">
<!doctype html>
<html>...</html>
</artifact>

Read the full file on GitHub · 82 lines

Files

What ships with it

2 files 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. 7d ago First seen · 82 lines · 57 tokens per session scan A a7ca4747d9f1

Subscribe to this mod's changes

blog-post is a skill published in the GitHub repository onfire7777/universal-ai-skills-library (16 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 753 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to blog-post, differing in 3 lines, and is treated as a copy.