Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/thatrebeccarae/claude-marketingnpx agentmods add rules/thatrebeccarae/claude-marketing/content-pipelineWrote 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/rules/thatrebeccarae/claude-marketing/content-pipeline)<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/content-pipeline"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/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.
<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/content-pipeline"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/content-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.00047 | $0.01701 |
| Opus 5 | $0.00023 | $0.00851 |
| Sonnet 5 | $0.00009 | $0.00340 |
| Haiku 4.5 | $0.00005 | $0.00170 |
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 9d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Pipeline
Orchestrate the full content creation workflow from research brief to published-ready content with social distribution pack.
What This Skill Does
Chains up to 3 agents in sequence:
- research-analyst — Generates a research brief on the topic
- editor-in-chief — Reviews the draft against voice, structure, SEO, and argument quality
- social-amplifier — Creates platform-specific distribution pack (LinkedIn, Twitter/X, email)
Users can enter at any stage or run the full pipeline.
How this differs from content-workflow: The content-workflow skill is a manual workflow guide with frameworks and checklists. This skill is the orchestration layer — it actually spawns subagents and manages the pipeline programmatically.
How to Use
/content-pipeline [topic or file path]
Full Pipeline (from scratch)
/content-pipeline "Why MCP is the new API"
Start from Existing Draft
/content-pipeline review ./drafts/article-draft.md
Social Pack Only
/content-pipeline distribute ./content/published-article.md
Workflow Stages
Stage 1: Research (optional — skip if draft exists)
- Spawn research-analyst agent with the topic
- Output:
./research-briefs/YYYY-MM-DD-topic-slug.md - User reviews brief, decides whether to proceed
Stage 2: Editorial Review
- Spawn editor-in-chief agent pointing at the draft/brief
- Output:
[draft-path]-review.mdsaved alongside the source - Agent provides: voice assessment, structure feedback, SEO evaluation, line-level notes, title variants
- User decides: publish as-is, revise, or iterate
Stage 3: Social Distribution
- Spawn social-amplifier agent pointing at the final content
- Output:
[content-path]-social-pack.mdsaved alongside the source - Generates: LinkedIn posts (2 variants), Twitter/X thread, email subject lines, pull quotes, hashtags
Configuration
Customizing Agents
The default agent chain uses Claude Code subagents with the Agent tool. To customize:
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.
- 9d ago First seen · 260 lines · 47 tokens per session scan A a60bbb23a687
content-pipeline is a cursor rule published in the GitHub repository thatrebeccarae/claude-marketing (133 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 1,701 once invoked, about $0.0002 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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.