analyze

analyze is a skill for Claude Code from pe-menezes/vibeflow. It costs 81 tokens per session (6,361 once invoked), scanned C, original, MIT.

A codebase analysis tool that examines a project's languages, structure, coding habits, and recurring patterns, then records the findings in a .vibeflow directory. It can analyze the whole project, selected folders, or a related dependency repository.

In plain words
What is it for?
Use it when setting up work on an unfamiliar repository, refreshing documentation after major changes, investigating one module, or recording patterns from a satellite repository.
Why use it?
It gives a coding agent durable project-specific context instead of making it rediscover conventions each time. Interactive review can also remove incorrect findings before they are saved.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

Part of the vibeflow plugin — 10 skills, 1 agent shipped together

Good fit Use it when setting up work on an unfamiliar repository, refreshing documentation…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pe-menezes/vibeflow/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.

Any agent
npx skills add pe-menezes/vibeflow --skill analyze
Clone the repo
git clone --depth 1 https://github.com/pe-menezes/vibeflow

Made for: Claude Code.

Or install vibeflow, the plugin that ships this one along with the rest of its 10 skills, 1 agent.

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/skills/pe-menezes/vibeflow/analyze.svg)](https://agentmods.dev/skills/pe-menezes/vibeflow/analyze)
Your own site
<a href="https://agentmods.dev/skills/pe-menezes/vibeflow/analyze"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/analyze.svg" alt="Measured on agentmods" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,361 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 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.00081 $0.06361
Opus 5 $0.00041 $0.03180
Sonnet 5 $0.00016 $0.01272
Haiku 4.5 $0.00008 $0.00636

Measured today against content hash 2c41432a0534, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade C, and why

analyze scanned grade C 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 today.

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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

Remove the temp directory (`rm -rf <temp_dir>`) whether the merge succeeded or
Origin

Copies of this mod

2 near-identical copies found in the catalogue:

plugins/vibeflow/skills/analyze/SKILL.md · 596 lines

How it starts

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

Description and examples

What it does: Scans the codebase and generates (or updates) .vibeflow/: index, conventions, and one pattern doc per significant pattern. Use once for project setup, then after big changes or to deep-dive into a module.

Examples:

  • analyze — First run or incremental (only re-analyzes what changed since last run).
  • analyze --fresh — Rebuild everything from scratch; ignore existing .vibeflow/.
  • analyze --scope src/app — Deep-dive into src/app only; requires .vibeflow/ to already exist. Enriches pattern docs with examples from that module.
  • analyze --interactive — Run analysis with interactive review: validate patterns, remove false positives, add tribal knowledge before saving.
  • analyze --fresh --interactive — Full rebuild with interactive review.
  • analyze --satellite https://github.com/org/design-system — Analyze a dependency repo, keep only patterns your code uses, merge into .vibeflow/patterns/satellite-<name>/.

Language

Detect the language of the user's conversation context. Write ALL output in that same language. Technical terms in English are acceptable regardless of the detected language. Section names in generated .vibeflow/ files may be in English (they are technical), but all descriptive text, analyses, observations, and final user reports should be in the detected language.

Web Search Policy

Use WebSearch and WebFetch only when local context (.vibeflow/, codebase, git history) is insufficient — an unfamiliar framework or API. Local first.

Perform a deep, adaptive analysis of this codebase. The goal is curated pattern documentation that every future spec, prompt pack, and audit uses to keep implementations on the project's real conventions.

Phase 0: Detect mode

Read .vibeflow/index.md directly by its path. Search, grep, and glob respect .gitignore, so they miss the directory and report it as absent.

Then read any flags in the user's current request (--fresh, --scope <path>, --interactive, --satellite <url>) and check whether git is available here.

Read the full file on GitHub · 596 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. today Changed · +5 lines 2c41432a0534
  2. 7d ago First seen · 591 lines · 81 tokens per session scan C e0df157e585e

Subscribe to this mod's changes

analyze is a skill published in the GitHub repository pe-menezes/vibeflow (29 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 6,361 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories