research

A command for finding search topics that competitors rank for but your site does not. A content gap is a relevant subject or keyword missing from your site's search visibility.

In plain words
What is it for?
It is for analyzing competitors, filtering out irrelevant or branded searches, scoring opportunities, and generating a dated report of content gaps.
Why use it?
It turns competitor rankings and search data into a prioritized list instead of requiring you to compare sites and keywords manually.

Command for Claude Code

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.

agentmods
npx agentmods add commands/seite-sh/seite/research
Clone the repo
git clone --depth 1 https://github.com/seite-sh/seite

Made for: Claude Code.

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 1,263 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.01263
Opus 5 $0.00000 $0.00632
Sonnet 5 $0.00000 $0.00253
Haiku 4.5 $0.00000 $0.00126

Measured 3d ago against content hash b32c8315783b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

research 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 3d 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.

seite-sh/.claude/commands/research.md · 131 lines

How it starts

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

Research Command

Use this command to conduct comprehensive SEO keyword research and competitive analysis before writing new content.

Usage

/research [topic]

What This Command Does

  1. Performs keyword research for static site generator and developer tool topics
  2. Analyzes top-ranking competitor content
  3. Identifies content gaps and opportunities
  4. Develops unique angle for seite perspective
  5. Creates detailed research brief for writing

Process

Keyword Research

  • Primary Keyword: Identify main target keyword for the topic
  • Search Volume & Difficulty: Research estimated monthly searches and competition level
  • Keyword Variations: Find semantic variations and long-tail opportunities
  • Related Questions: Discover what people are actually asking (People Also Ask, forums, Reddit)
  • Search Intent: Determine if intent is informational, navigational, commercial, or transactional
  • Topic Cluster: Identify how this topic fits into seite content clusters

Competitive Analysis

  • Top 10 SERP Review: Analyze the top 10 ranking articles for target keyword
  • Content Length: Note word count of top-performing articles (benchmark target)
  • Common Themes: What topics/sections do all top articles cover?
  • Content Gaps: What's missing from competitor coverage?
  • Unique Angles: What perspectives or insights are underexplored?
  • Featured Snippets: Identify if there's a featured snippet opportunity
  • Domain Authority: Note which competitors rank (indie blogs vs. major publications)

Context Integration

  • seite Advantage: How can seite product features naturally enhance this content?
  • Brand Alignment: Check @context/brand-voice.md for messaging fit
  • Existing Content: Review @context/internal-links-map.md for related seite articles
  • Target Keywords: Cross-reference with @context/target-keywords.md priority list
  • SEO Guidelines: Ensure research aligns with @context/seo-guidelines.md requirements

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

  1. 3d ago First seen · 131 lines · 0 tokens per session scan A b32c8315783b

Subscribe to this mod's changes

research is a command published in the GitHub repository seite-sh/seite (19 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,263 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.