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.
curl -O https://raw.githubusercontent.com/charlesdove977/goviralbro/main/.claude/commands/viral-discover.mdgit clone --depth 1 https://github.com/charlesdove977/goviralbroWrote 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/commands/charlesdove977/goviralbro/viral-discover)<a href="https://agentmods.dev/commands/charlesdove977/goviralbro/viral-discover"><img src="https://agentmods.dev/badge/commands/charlesdove977/goviralbro/viral-discover/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/commands/charlesdove977/goviralbro/viral-discover"><img src="https://agentmods.dev/badge/commands/charlesdove977/goviralbro/viral-discover.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.00000 | $0.11146 |
| Opus 5 | $0.00000 | $0.05573 |
| Sonnet 5 | $0.00000 | $0.02229 |
| Haiku 4.5 | $0.00000 | $0.01115 |
Grade A, and why
viral-discover scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://www.googleapis.com/youtube/v3/search?part=snippet&q=${HANDLE}&type=channel&key=${YOUTUBE_API_KEY}" Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
v = subprocess.check_output(['yt-dlp', '--version']).decode().strip() How it starts
The opening of the file, as written. The whole thing — 960 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/viral:discover — Multi-Platform Topic Discovery
You are running the Viral Command discovery engine. Your job is to find winning content ideas through competitor analysis, keyword-based search (YouTube, Reddit, GitHub), or both — all scored against the creator's ICP.
Arguments: $ARGUMENTS
Flags:
| Flag | Description |
|---|---|
--competitors |
Skip mode selection, run competitor scrape only |
--keywords |
Skip mode selection, run keyword search only (YouTube + Reddit + GitHub) |
--all |
Skip mode selection, run both competitor scrape + keyword search |
--deep |
Use deep mode for trend queries (slower, more thorough) |
| (none) | Interactive — asks which discovery mode to use |
⚠️ EXECUTION ORDER — READ THIS FIRST
You MUST follow this exact sequence. Do NOT skip steps or jump ahead.
- Phase A: Load agent brain (read
data/agent-brain.json) - Phase A.5: Show keywords table + ask discovery mode [C/K/B] — STOP HERE AND WAIT FOR USER INPUT
- Only after user responds: proceed to Phase 1 (competitor), Phase 1.5 (keyword), or both
The #1 rule: After loading the brain, your VERY FIRST output to the user must be the keyword table and mode selector from Phase A.5. Do NOT start fetching YouTube data, Instagram data, or any API calls before the user picks a mode. No exceptions.
Phase A: Load Agent Brain
Read the agent brain to understand who the creator is:
@data/agent-brain.json
Extract these fields:
identity— who the creator is, niche, tonecompetitors[]— competitor list with platform + handleicp.segments[],icp.pain_points[],icp.goals[]— scoring context + CCN fit evaluationpillars[]— content themes + keywordslearning_weights— scoring multipliersplatforms.api_keys_configured— available APIs
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."
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.
- 11d ago First seen · 960 lines · 0 tokens per session scan A 176bba4391dd
viral-discover is a command published in the GitHub repository charlesdove977/goviralbro (264 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 11,146 tokens. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.