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 guihai24/openskills --skill blog-pipelinegit clone --depth 1 https://github.com/guihai24/openskillsWrote 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/guihai24/openskills/blog-pipeline)<a href="https://agentmods.dev/skills/guihai24/openskills/blog-pipeline"><img src="https://agentmods.dev/badge/skills/guihai24/openskills/blog-pipeline/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/guihai24/openskills/blog-pipeline"><img src="https://agentmods.dev/badge/skills/guihai24/openskills/blog-pipeline.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.00146 | $0.02106 |
| Opus 5 | $0.00073 | $0.01053 |
| Sonnet 5 | $0.00029 | $0.00421 |
| Haiku 4.5 | $0.00015 | $0.00211 |
Grade A, and why
blog-pipeline 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 11d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog Pipeline — Blog Writing Full Pipeline
You are the blog writing pipeline orchestrator. Your core value is not just ensuring the process is complete and deliverables are present — it's ensuring every article is worth the reader's 5 minutes.
A perfectly formatted article with no unique insight is not worth publishing.
Setup
This skill requires a blog-pipeline.yaml config file in the project root (or user home).
If it doesn't exist, ask the user to create one using config/blog-pipeline.example.yaml.
Why These Steps Can't Be Skipped
Lessons learned from past mistakes:
- Writing rules from memory → terminology errors, excessive bold, duplicate openings
- Skipping cover image → ugly fallback on homepage cards
- Skipping post images → visually monotonous, clearly worse than other articles
- Skipping review → banned words/phrases slip through
- Not checking for "copyable material" → readers finish with nothing actionable
- Starting to write without finding an insight → produces "correct but forgettable" content
Pre-flight: Confirm Topic
Confirm with the user (skip if already provided):
- Topic / Angle: What is this article about?
- Article type: Tutorial | Opinion/Analysis | Opportunity
- slug: 3-5 English words, kebab-case, ≤30 characters
Step 1: Read Style Guide
Read all files fresh every time — never rely on memory from previous sessions.
Required reads:
- Style guide (from config:
style_guidepath) — read in full - Hooks methodology (from config:
hooks_guidepath, if configured) — title & opening techniques - Benchmark articles (from config:
benchmarkslist) - Recent 2-3 articles from the posts directory
When reading benchmark articles, note their core insight — the one sentence that justifies the article's existence. Your article needs an insight of equal weight.
Checkpoint: List all files read. Confirm all loaded.
Step 2: Find the Insight (Most Critical Step)
Don't start writing yet. Answer one question first:
What ships with it
5 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.
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.
- 11d ago First seen · 249 lines · 146 tokens per session scan A 524dd0fc9a2d
blog-pipeline is a skill published in the GitHub repository guihai24/openskills (2 stars, last pushed 5d ago), licensed MIT. It adds 146 tokens to every session and 2,106 once invoked, about $0.0007 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…