content-writer

content-writer is a skill for Claude Code, Codex from ViryaZheng/recomby-geo. It costs 163 tokens per session (2,257 once invoked), scanned C, original, MIT.

A writing workflow for creating or improving blog posts, landing pages, and other long-form web copy. It uses search-focused and reader-focused writing guidelines.

In plain words
What is it for?
Use it to write blog posts, service and product pages, landing pages, location pages, and rewrites of existing web content.
Why use it?
It gives a defined process for turning a topic, keyword, or brief into useful page copy, or for finding problems in existing content.

Skill for Claude CodeCodex

Written for Claude Code and Codex: argument-hint in frontmatter, but also reads ~/.codex or $CODEX_HOME. Also seen: reads .claude/ paths; mentions Codex.

Part of the recomby-geo plugin — 9 skills, 7 commands shipped together

Good fit Use it to write blog posts, service and product pages, landing pages, location pages, and rewrites of existing web content.

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

Made for: Claude Code, Codex.

Or install recomby-geo, the plugin that ships this one along with the rest of its 9 skills, 7 commands.

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-writer

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/viryazheng/recomby-geo/content-writer"><img src="https://agentmods.dev/badge/skills/viryazheng/recomby-geo/content-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 163 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,257 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00163 $0.02257
Opus 5 $0.00081 $0.01128
Sonnet 5 $0.00033 $0.00451
Haiku 4.5 $0.00016 $0.00226

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

Security

Grade C, and why

content-writer scanned grade C with 2 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

CONTENT_REF=$(find ~/.claude/plugins ~/.claude/skills ~/.codex/skills .agents/skills -name "content-writing.md" -path "*content-writer*" 2>/dev/null | head -1)

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

CONTENT_REF=$(find ~/.claude/plugins ~/.claude/skills ~/.codex/skills .agents/skills -name "content-writing.md" -path "*content-writer*" 2>/dev/null | head -1)
plugins/recomby-geo/skills/content-writer/SKILL.md · 258 lines

How it starts

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

Content Writer

You are a senior content strategist who writes content that ranks on Google AND genuinely helps readers. You combine SEO best practices with strong editorial standards. Every piece must pass Google's "helpful content" bar — it should be the last click the reader needs.

You handle three jobs:

  1. New blog post — from a keyword or topic
  2. New landing page — service, product, location, or comparison page
  3. Content improvement — audit and rewrite an existing page

Step 1 — Determine the Job

Infer from the user's message. If obvious, skip asking.

Signals:

  • "blog post about X", "how-to guide", "article about X", "listicle" → Blog post
  • "landing page", "service page", "product page", "pricing page", "location page" → Landing page
  • "improve this page", "rewrite", "make this better", URL or file path provided → Content improvement

If ambiguous: "Are you looking for a blog post (educational), a landing page (conversion-focused), or improving an existing page?"


Step 2 — Gather Context

Collect what you need. Don't ask for things you can infer.

For new content (blog post or landing page):

  • Target keyword (required) — the primary query to rank for
  • Audience — who is this for?
  • Site/brand context — what does the business do, value prop?
  • Existing pages — related pages on the site to link to?
  • Competitors — what currently ranks? (offer to research if you have web access)

For content improvement:

  • The content — read the existing page (URL via firecrawl/web, or file path)
  • Target keyword — ask if not obvious from the content
  • Goal — better rankings, better conversion, or both?

If spawned by seo-analysis, this context is already provided. Use it directly.


Step 3 — Read the Guidelines

Locate and read the content writing reference:

CONTENT_REF=$(find ~/.claude/plugins ~/.claude/skills ~/.codex/skills .agents/skills -name "content-writing.md" -path "*content-writer*" 2>/dev/null | head -1)
if [ -z "$CONTENT_REF" ]; then
  echo "WARNING: Could not find content-writing.md reference"
else
  echo "Reference at: $CONTENT_REF"
fi

Read the full file on GitHub · 258 lines

Files

What ships with it

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

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 · 258 lines · 163 tokens per session scan C 07bf2ebd5a61

Subscribe to this mod's changes

content-writer is a skill published in the GitHub repository ViryaZheng/recomby-geo (454 stars, last pushed 2mo ago), licensed MIT. It adds 163 tokens to every session and 2,257 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it C with 2 findings (reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.