cf-brief

cf-brief is a skill for Claude Code from indranilbanerjee/neels-plugins. It costs 29 tokens per session (4,598 once invoked), scanned A, a copy of cf-brief, MIT.

A research-based content brief writer that turns a keyword or topic into guidance for producing an article or other content. It covers search intent, competitor content, audience problems, keywords, and a suggested outline.

In plain words
What is it for?
Use it to research a topic, identify search intent and competitor gaps, choose an angle, create an outline, and prepare a brief for approval.
Why use it?
It gives writers and stakeholders a structured plan before drafting starts, reducing unclear topics, weak outlines, and content that does not match what people are searching for.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it to research a topic, identify search intent and competitor gaps, choose an angle, create an outline, and prepare a brief for approval.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/indranilbanerjee/neels-plugins/cf-brief
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 indranilbanerjee/neels-plugins --skill cf-brief
Clone the repo
git clone --depth 1 https://github.com/indranilbanerjee/neels-plugins

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.

agentmods badge for cf-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/cf-brief/github.svg)](https://agentmods.dev/skills/indranilbanerjee/neels-plugins/cf-brief)
Your own site
<a href="https://agentmods.dev/skills/indranilbanerjee/neels-plugins/cf-brief"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/cf-brief/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 cf-brief

Your own site · 80×15
<a href="https://agentmods.dev/skills/indranilbanerjee/neels-plugins/cf-brief"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/cf-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,598 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 91% 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.00029 $0.04598
Opus 5.5 $0.00012 $0.01839
Sonnet 5.5 $0.00006 $0.00920
Haiku 4.5 $0.00003 $0.00460

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

Security

Grade A, and why

cf-brief 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 2d 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

91% identical to cf-brief — 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.

hermes/digital-marketing-pro/content/skills/cf-brief/SKILL.md · 335 lines

How it starts

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

Content Brief Generator

Generate a comprehensive, research-backed content brief from a keyword or topic. The brief includes keyword data, competitor content analysis, search intent classification, audience pain points, a recommended outline, and an actionable SEO strategy — everything a writer needs to produce high-ranking content on the first draft.

When to Use

Use /contentforge:cf-brief when:

  • You need a structured content brief before starting production with /contentforge:create-content
  • You want data-driven keyword research to inform topic selection
  • You need to analyze competitor content to find gaps and differentiation angles
  • You're planning a content calendar and need briefs for multiple upcoming pieces
  • A client or stakeholder requires a brief for approval before production begins
  • You want to understand search intent before committing to a content type

For direct content production (brief + draft in one step), use /contentforge:create-content instead. For multiple briefs, run /contentforge:cf-brief once per topic.

What This Command Does

  1. Keyword Research — Primary keyword analysis with search volume, keyword difficulty, related and semantically adjacent terms, and long-tail opportunities
  2. Competitor Content & E-E-A-T Analysis — Analyze top 5 ranking pages for word count, structure, key points covered, content gaps, unique angles, and E-E-A-T signals (author credentials, original research, first-hand experience)
  3. Search Intent Classification — Determine whether the query is informational, commercial, transactional, or navigational, and recommend content type accordingly
  4. Audience Pain Points & Questions — Map target audience needs, common questions, forum discussions, and "People Also Ask" patterns
  5. Recommended Outline — Generate a structured outline with title options, section descriptions, word count allocations, and citation targets per section
  6. SEO Strategy — Keyword placement plan, meta title/description recommendations, internal linking opportunities, featured snippet potential, and schema markup suggestions
  7. AEO/GEO Strategy — AI Overview presence check, citation-worthiness checklist, entity consistency, answer-block recommendations, honest llms.txt note (not a ranking/citation signal)
  8. Success Metrics — Define measurable goals: target word count, minimum citations, readability target, quality score goal (8.5+)

Read the full file on GitHub · 335 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. 2d ago First seen · 335 lines · 29 tokens per session scan A bd876e85b912

Subscribe to this mod's changes

cf-brief is a skill published in the GitHub repository indranilbanerjee/neels-plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 4,598 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to cf-brief, differing in 0 lines, and is treated as a copy.