analyze

analyze is a command for Claude Code from Galbaz1/video-research-mcp. It costs 11 tokens per session (1,175 once invoked), scanned B, original, MIT.

A content-analysis command for examining a web page, file, directory, or pasted text.

In plain words
What is it for?
Use it to analyze URLs, local files, folders, or text, then save the results and create a knowledge-graph view when applicable.
Why use it?
It turns source material into a structured summary with key points, entities, document structure, and a quality assessment.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; names the AskUserQuestion tool.

Part of the gr plugin — 12 skills, 17 commands, 7 agents shipped together

Good fit Use it to analyze URLs, local files, folders, or text, then save the results and create a knowledge-graph view when applicable.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/galbaz1/video-research-mcp/analyze
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.

Clone the repo
git clone --depth 1 https://github.com/Galbaz1/video-research-mcp

Made for: Claude Code.

Or install gr, the plugin that ships this one along with the rest of its 12 skills, 17 commands, 7 agents.

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 analyze

README.md
[![agentmods](https://agentmods.dev/badge/commands/galbaz1/video-research-mcp/analyze/github.svg)](https://agentmods.dev/commands/galbaz1/video-research-mcp/analyze)
Your own site
<a href="https://agentmods.dev/commands/galbaz1/video-research-mcp/analyze"><img src="https://agentmods.dev/badge/commands/galbaz1/video-research-mcp/analyze/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 analyze

Your own site · 80×15
<a href="https://agentmods.dev/commands/galbaz1/video-research-mcp/analyze"><img src="https://agentmods.dev/badge/commands/galbaz1/video-research-mcp/analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 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,175 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00011 $0.01175
Opus 5 $0.00005 $0.00588
Sonnet 5 $0.00002 $0.00235
Haiku 4.5 $0.00001 $0.00118

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

Security

Grade B, and why

analyze scanned grade B with 1 finding 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 9d 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.

a. Determine the memory directory: find the `.claude/` project memory path for the current working directory. Use `Glob` on `~/.claude/projects/*/memory/` to find the active project memory path if needed.
commands/analyze.md · 129 lines

How it starts

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

Content Analysis: $ARGUMENTS

Analyze the provided content with progressive memory saving and automatic knowledge-graph visualization.

Phase 1: Analyze

  1. Determine the input type from "$ARGUMENTS":
    • If it starts with http:// or https://: use content_analyze with url parameter
    • If it looks like a file path (contains / or .extension): use content_analyze with file_path parameter
    • If it's a directory path (ends with / or is a known directory): use content_batch_analyze with directory parameter and mode="compare"
    • Otherwise: use content_analyze with text parameter
  2. Use instruction="Provide a comprehensive analysis including title, summary, key points, important entities (people, organizations, concepts, technologies), document structure, and quality assessment."

Phase 2: Present & Save Initial Results

  1. Present results clearly:

    • Title and Source
    • Summary (2-3 sentences)
    • Key Points (bulleted)
    • Entities (people, organizations, concepts)
    • Quality Assessment
  2. Immediately save initial results: a. Determine the memory directory: find the .claude/ project memory path for the current working directory. Use Glob on ~/.claude/projects/*/memory/ to find the active project memory path if needed. b. Generate a slug from the content title or source: lowercase, hyphens, no special chars, max 50 chars (e.g., "Attention Is All You Need" → attention-is-all-you-need, a URL like arxiv.org/abs/2401.12345arxiv-2401-12345) c. Use Write to save at <memory-dir>/gr/analysis/<slug>/analysis.md:

---
source: <url, file path, or "pasted text">
analyzed: <ISO 8601 timestamp>
updated: <ISO 8601 timestamp>
entities:
  people: <count>
  organizations: <count>
  concepts: <count>
  technologies: <count>
---

# <Title>

> Source: <url, file path, or "pasted text">
> Analyzed on <YYYY-MM-DD HH:MM>

## Summary  <!-- <YYYY-MM-DD HH:MM> -->

<2-3 sentence summary>

## Key Points  <!-- <YYYY-MM-DD HH:MM> -->

<Bulleted key points>

## Entities  <!-- <YYYY-MM-DD HH:MM> -->

### People
- <Person 1> — <role/context>

### Organizations
- <Org 1> — <context>

### Concepts
- <Concept 1> — <brief definition>

### Technologies
- <Tech 1> — <context>

## Quality Assessment  <!-- <YYYY-MM-DD HH:MM> -->

<Assessment of content quality, reliability, completeness>

Read the full file on GitHub · 129 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. 9d ago First seen · 129 lines · 11 tokens per session scan B 5446def1bcc5

Subscribe to this mod's changes

analyze is a command published in the GitHub repository Galbaz1/video-research-mcp (23 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 1,175 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.