A command that turns discovered topics into content ideas for different formats, using a contrast between what people commonly believe and a surprising explanation.

Use it to develop angles for long-form and short-form content, with the creator’s audience, themes, competitors, and marketing direction taken into account.

It connects each idea to a target audience, audience problem, and next action, reducing the work of shaping a topic into focused content.

How charlesdove977/goviralbro configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to charlesdove977/goviralbro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/charlesdove977/goviralbro/main/.claude/commands/viral-angle.md

Clone the repo

git clone --depth 1 https://github.com/charlesdove977/goviralbro

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/charlesdove977/goviralbro/viral-angle/github.svg)](https://agentmods.dev/commands/charlesdove977/goviralbro/viral-angle)

Your own site

<a href="https://agentmods.dev/commands/charlesdove977/goviralbro/viral-angle"><img src="https://agentmods.dev/badge/commands/charlesdove977/goviralbro/viral-angle/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/charlesdove977/goviralbro/viral-angle"><img src="https://agentmods.dev/badge/commands/charlesdove977/goviralbro/viral-angle.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 5,120 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.05120
Opus 5.5	$0.00000	$0.02048
Sonnet 5.5	$0.00000	$0.01024
Haiku 4.5	$0.00000	$0.00512

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

Security

Grade A, and why

viral-angle 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 2mo 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.

.claude/commands/viral-angle.md · 517 lines

How it starts

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

/viral:angle — Contrast Formula Angle Development

You are running the Viral Command angle engine. Your job is to transform discovered topics into format-specific content angles using the Contrast Formula (common belief → surprising truth), with funneling/CTA direction baked into every angle.

Arguments: $ARGUMENTS

Phase A: Load Agent Brain

Read the agent brain to understand the creator's identity, audience, and monetization strategy:

@data/agent-brain.json

Extract these fields:

identity — name, brand, niche, tone, differentiator
icp.segments[] — audience segments (for target_audience)
icp.pain_points[] — audience pains (for pain_addressed)
icp.goals[] — what the audience wants to achieve
pillars[] — content themes + keywords
monetization — primary_funnel, secondary_funnels, cta_strategy (default_cta, community_url, website_url)
audience_blockers[] — lies the audience believes (for blocker destruction matching)
content_jobs — pillar-to-job mapping (build_trust, demonstrate_capability, drive_action)
competitors[] — competitor handles + platforms (for differentiation)

Formats to generate angles for:

longform — YouTube longform videos
shortform — cross-posted to Shorts, Reels, AND TikTok (one shortform = one video posted to all 3)
linkedin — LinkedIn text posts (separate format)

If the brain is empty or identity.name is blank: Stop and say: "Your agent brain isn't set up yet. Run /viral:onboard first to tell me who you are and what you create."

Phase A.5: Competitor Angle Analysis (--competitors mode)

If $ARGUMENTS contains --competitors: Run a standalone competitor angle analysis instead of developing angles for a single topic. After displaying the analysis, exit — this is analysis-only, not angle generation.

Step 1: Load competitor recon data

Read data/recon/reports/ for skeleton analysis reports
Read data/recon/competitors/{handle}/ for each competitor listed in agent-brain.json
If no recon data found: Stop and say: "No competitor data found. Run the Recon UI first: ./scripts/run-recon-ui.sh"

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

2mo ago First seen · 517 lines · 0 tokens per session scan A 8d8aae65218b

Subscribe to this mod's changes

viral-angle is a command published in the GitHub repository charlesdove977/goviralbro (271 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,120 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.

Marketing and SEO

viral-angle next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
viral-anglecharlesdove977/goviralbro	Command	271	7mo ago	MIT	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

goviralbro: Command for Claude Code