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 agentmods add skills/ericrisco/rsc-harness/content-enginenpx skills add ericrisco/rsc-harness --skill content-enginegit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/content-engine)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/content-engine"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/content-engine.svg" alt="Measured on agentmods" 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 | $0.00083 | $0.02973 |
| Opus 5 | $0.00042 | $0.01486 |
| Sonnet 5 | $0.00017 | $0.00595 |
| Haiku 4.5 | $0.00008 | $0.00297 |
Grade A, and why
content-engine 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 4d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Engine — The Calendar and the Pipeline That Feeds It
The factory floor and the production schedule, not the words off any single station. You own two machines: the calendar (what gets made and when — a dated, slotted plan anchored to pillars, so "what do we post Thursday?" is a lookup, not a weekly panic) and the pipeline (how each slot moves from idea to publish-ready through stage gates, so output is consistent regardless of who writes). You do not write the pieces and you do not publish them — you decide what gets made, you spec the brief, and you route each station to a specialist.
Content fails not from one bad post but from no system: no documented cadence, no brief, no stage gate, pillars that never get atomized. ~78% of high-performing content teams run a documented strategy and see ~3x the engagement of teams without one (InfluenceFlow, 2026). This skill is that system.
Ground first (STOP gate)
You plan content for a real brand; you do not invent its strategy. Before building anything, read what already exists.
- Read the brand study and pillars from
02-DOCS/(the project wiki). If the project uses the harness convention, that is02-DOCS/wiki/— see../harness/SKILL.md. - If voice/tone is missing → STOP. Route the user to
brand-voiceto codify do/don't words and voice samples. Do not invent a voice; a calendar built on a guessed voice produces off-brand drafts at every station. - If pillars/clusters/keywords are missing → STOP for the research half. Route topic-cluster and keyword work to
seo-geo. You consume pillars and clusters; you do not derive them from search data — that is its job. - Persist the calendar of record under
02-DOCS/wiki/content/and raw inputs (interviews, exports) under02-DOCS/raw/content/. Why: the calendar must be a durable artifact of record, not a chat message that scrolls away. - Cite what you grounded in (e.g. "pillars from
02-DOCS/wiki/brand-study.md"). If you grounded in nothing, say so and stop.
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.
- 4d ago First seen · 153 lines · 83 tokens per session scan A 76dc62942ca3
content-engine is a skill published in the GitHub repository ericrisco/rsc-harness (60 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 2,973 once invoked, about $0.0004 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 skills, from other repositories
content-audit
Content file quality audit across 8 dimensions (CC1-CC8): encoding artifacts (NBSP, mojibake, zero-width), markdown syntax (broken italic, orphan backslash), CMS migration artifacts (Joomla/WordPress/PHP), frontmatter quality, image integrity, link integrity with anchor validation, content completeness, and…
content-migration
Compare old CMS page with new SSG page after migration. Finds missing headings, paragraphs, images, CTAs, tables, forms. Optionally patches safe gaps in local .md files. Use when content was migrated from Joomla/WordPress/ Drupal to Astro/Hugo/Next.js and you need to verify nothing was lost. Flags: --old , --new …
content-expand
Expand and optimize existing articles. Adds new sections, deepens thin content, and applies the same quality pipeline as write-article (anti-slop, BLUF, GEO signals, humanization, multi-schema). Includes web search research about the topic and auto-discovery of internal links from your content collection. Replaces…
content-fix
Apply fixes from content-audit findings. Reads audit JSON, classifies fixes by safety tier (SAFE/MODERATE), applies templates per fix type. Handles encoding artifacts (NBSP, mojibake), broken markdown, CMS migration debris, and typography issues. Modes: default (SAFE only), --auto (SAFE+MODERATE), --dry-run, --finding…
Article Repurposer
Takes a long-form article and repurposes it into multiple formats: tweet thread, LinkedIn post, TL;DR, and key quotes.
channel-formats
Transforms one piece of content into each marketing channel's native format — length, structure, hooks, and conventions — across LinkedIn, X threads, newsletters, Instagram, YouTube, short video, and blogs. Use when reformatting content for a specific channel. Trigger with "channel format", "adapt for LinkedIn", or…