What is content-pipeline?

A command that runs a multi-step content production workflow using several agents. The workflow researches a topic, analyzes it, writes and edits content, checks search visibility, and performs a final review.

Use it to create blog posts, guides, or landing pages from a topic or brief, with optional keywords and audience details.

It organizes a content task into dependent stages so research, writing, editing, and review happen in a defined order.

content-pipeline — Command for Claude Code by arturseo-geo

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.

Clone the repo

git clone --depth 1 https://github.com/arturseo-geo/content-pipeline-skill

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/arturseo-geo/content-pipeline-skill/content-pipeline/github.svg)](https://agentmods.dev/commands/arturseo-geo/content-pipeline-skill/content-pipeline)

Your own site

<a href="https://agentmods.dev/commands/arturseo-geo/content-pipeline-skill/content-pipeline"><img src="https://agentmods.dev/badge/commands/arturseo-geo/content-pipeline-skill/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/arturseo-geo/content-pipeline-skill/content-pipeline"><img src="https://agentmods.dev/badge/commands/arturseo-geo/content-pipeline-skill/content-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,018 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01018
Opus 5	$0.00000	$0.00509
Sonnet 5	$0.00000	$0.00204
Haiku 4.5	$0.00000	$0.00102

Measured 11d ago against content hash 157ec8f76c02, 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

Copies of this mod

1 near-identical copy found in the catalogue:

content-pipeline — 100% identical, 0 lines differ

commands/content-pipeline.md · 120 lines

How it starts

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

/content-pipeline

Run the full multi-agent content production pipeline.

Usage

/content-pipeline "topic or brief"
/content-pipeline "topic or brief" --type [blog|guide|landing-page]
/content-pipeline "topic or brief" --keyword "primary keyword" --audience "target audience"

What This Command Does

Creates the brief — writes .claude/pipeline/brief.md from your input
Phase 1 (parallel) — spawns Research Agent and Analytics Agent simultaneously
Waits for both to complete (checks for COMPLETE status lines)
Phase 2 — spawns Writer Agent (depends on Phase 1)
Phase 3 — spawns Editor Agent (depends on Writer)
Phase 4 — spawns SEO/GEO Agent (depends on Editor)
Phase 5 — spawns Master Agent (reviews all outputs)
Pauses — presents master-review.md for your approval

Step-by-Step Execution

Step 1: Create pipeline directory and brief

mkdir -p .claude/pipeline

Write .claude/pipeline/brief.md:

# Content Brief
Topic: [extracted from user input]
Content type: [blog post / guide / landing page — inferred or from --type flag]
Primary keyword: [from --keyword flag or infer from topic]
Target audience: [from --audience flag or infer]
Additional requirements: [any other specifics from user input]
Created: [timestamp]

Step 2: Spawn Phase 1 agents in parallel

Dispatch two Task tool calls simultaneously:

Task 1 — Research Agent:

Read .claude/agents/research-agent.md for your instructions.
Input file: .claude/pipeline/brief.md
Output file: .claude/pipeline/research.md

Task 2 — Analytics Agent:

Read .claude/agents/analytics-agent.md for your instructions.
Input file: .claude/pipeline/brief.md
Output file: .claude/pipeline/analytics.md

Wait until both files contain their COMPLETE status line before proceeding.

Step 3: Spawn Writer Agent

Read .claude/agents/writer-agent.md for your instructions.
Input files: .claude/pipeline/brief.md, .claude/pipeline/research.md, .claude/pipeline/analytics.md
Output file: .claude/pipeline/draft.md

Read the full file on GitHub · 120 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.

11d ago First seen · 120 lines · 0 tokens per session scan A 157ec8f76c02

Subscribe to this mod's changes

content-pipeline is a command published in the GitHub repository arturseo-geo/content-pipeline-skill (20 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,018 tokens. 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-30.

Claude Code Marketing and SEO Writing and docs ai-writing anthropic automation content-creation content-pipeline

content-pipeline