content-pipeline

content-pipeline is a skill for Claude Code, Codex from arturseo-geo/claude-code-skills. It costs 157 tokens per session (1,864 once invoked), scanned A, a copy of content-pipeline, MIT.

A coordinated workflow in which specialist agents research, write, edit, improve search visibility, and review content before publication.

In plain words
What is it for?
It is for producing blog posts, landing pages, and other content using research, analytics, drafting, editing, SEO, and final review stages.
Why use it?
It separates different content tasks and adds a review pause so unfinished or inaccurate material is caught before publishing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths.

Good fit It is for producing blog posts, landing pages, and other content using research, analytics, drafting, editing, SEO, and final review stages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/arturseo-geo/claude-code-skills/content-pipeline
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 arturseo-geo/claude-code-skills --skill content-pipeline
Clone the repo
git clone --depth 1 https://github.com/arturseo-geo/claude-code-skills

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 content-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/arturseo-geo/claude-code-skills/content-pipeline/github.svg)](https://agentmods.dev/skills/arturseo-geo/claude-code-skills/content-pipeline)
Your own site
<a href="https://agentmods.dev/skills/arturseo-geo/claude-code-skills/content-pipeline"><img src="https://agentmods.dev/badge/skills/arturseo-geo/claude-code-skills/content-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.

agentmods 80×15 button for content-pipeline

Your own site · 80×15
<a href="https://agentmods.dev/skills/arturseo-geo/claude-code-skills/content-pipeline"><img src="https://agentmods.dev/badge/skills/arturseo-geo/claude-code-skills/content-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 157 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,864 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 100% 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.00157 $0.01864
Opus 5 $0.00078 $0.00932
Sonnet 5 $0.00031 $0.00373
Haiku 4.5 $0.00016 $0.00186

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

Security

Grade A, and why

content-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.

Origin

This is a copy

100% identical to content-pipeline — 0 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/content-pipeline/SKILL.md · 209 lines

How it starts

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

Content Pipeline Skill

A multi-agent content production workflow. Six specialist agents collaborate, each writing outputs to .claude/pipeline/. The Master Agent reviews all outputs and halts for your approval before anything is published.

Pipeline Overview

User request
    ↓
Orchestrator (you — or auto via /content-pipeline command)
    ↓
[Phase 1 — parallel]
  Research Agent     → .claude/pipeline/research.md
  Analytics Agent    → .claude/pipeline/analytics.md
    ↓
[Phase 2 — sequential, depends on Phase 1]
  Writer Agent       → .claude/pipeline/draft.md
    ↓
  Editor Agent       → .claude/pipeline/edited-draft.md
    ↓
  SEO/GEO Agent      → .claude/pipeline/seo-report.md
                     → .claude/pipeline/final-draft.md
    ↓
[Phase 3]
  Master Agent       → .claude/pipeline/master-review.md
    ↓
  ⏸ HUMAN APPROVAL — review master-review.md, then say "approved" or give feedback
    ↓
  Publish / revise

Agent Roster

Load agent files from .claude/agents/ as needed:

Agent File Role
Research research-agent.md Web search, topic analysis, competitor content
Analytics analytics-agent.md GSC + GA4 + DataForSEO data pull
Writer writer-agent.md Draft creation from research brief
Editor editor-agent.md Quality, accuracy, brand voice, humanisation
SEO/GEO seo-geo-agent.md Keyword optimisation, schema, GEO readiness
Master master-agent.md Final QA gate, human-ready summary

Running the Pipeline

Full pipeline (recommended)

/content-pipeline "topic or brief here"

Single agent (re-run one stage)

/run-agent writer "rewrite the draft with a more conversational tone"
/run-agent seo "re-optimise for keyword: [new keyword]"

Review current pipeline state

/pipeline-status

Pipeline Output Files

All files written to .claude/pipeline/ (gitignored by default):

.claude/pipeline/
├── brief.md           ← input: topic + requirements
├── research.md        ← Research Agent output
├── analytics.md       ← Analytics Agent output
├── draft.md           ← Writer Agent output
├── edited-draft.md    ← Editor Agent output
├── seo-report.md      ← SEO Agent analysis
├── final-draft.md     ← SEO Agent optimised draft
├── master-review.md   ← Master Agent final review
└── approved/          ← content that passed approval

Read the full file on GitHub · 209 lines

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. 11d ago First seen · 209 lines · 157 tokens per session scan A 3d8115d57806

Subscribe to this mod's changes

content-pipeline is a skill published in the GitHub repository arturseo-geo/claude-code-skills (11 stars, last pushed 5mo ago), licensed MIT. It adds 157 tokens to every session and 1,864 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to content-pipeline, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

security-compliance

Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.

sangrokjung/claude-forge · 56 tokens

stride-analysis-patterns

Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.

sangrokjung/claude-forge · 30 tokens

cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…

sangrokjung/claude-forge · 183 tokens

manage-skills

A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.

sangrokjung/claude-forge · 54 tokens

blind-spot-pass

Use before starting work in a domain you don't know well, to surface the "unknown unknowns" — the things you don't even know to ask about — and learn just enough to prompt and decide well. Implements the "blind spot pass" pattern from Anthropic's Fable "finding your unknowns" field guide. Triggers when you say "I'm…

sangrokjung/claude-forge · 221 tokens

verify-implementation

A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.

sangrokjung/claude-forge · 37 tokens