What is openlore-analyze-codebase?

A guide for running OpenLore’s full static analysis of a codebase. Static analysis examines source code structure without relying on guesses from a language model.

Use it to assess a project, summarize its architecture, count files and functions, find high-priority refactoring issues, and identify routes and other structural details.

It gives a factual map of the project and highlights call relationships, refactoring problems, duplicate code, frameworks, and domains.

openlore-analyze-codebase — Skill by clay-good/OpenLore

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 clay-good/OpenLore --skill openlore-analyze-codebase

Clone the repo

git clone --depth 1 https://github.com/clay-good/OpenLore

Made for: Claude Code, Codex.

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/skills/clay-good/openlore/openlore-analyze-codebase/github.svg)](https://agentmods.dev/skills/clay-good/openlore/openlore-analyze-codebase)

Your own site

<a href="https://agentmods.dev/skills/clay-good/openlore/openlore-analyze-codebase"><img src="https://agentmods.dev/badge/skills/clay-good/openlore/openlore-analyze-codebase/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/skills/clay-good/openlore/openlore-analyze-codebase"><img src="https://agentmods.dev/badge/skills/clay-good/openlore/openlore-analyze-codebase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 925 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00048	$0.00925
Opus 5.5	$0.00019	$0.00370
Sonnet 5.5	$0.00010	$0.00185
Haiku 4.5	$0.00005	$0.00093

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

Security

Grade A, and why

openlore-analyze-codebase 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 1mo 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.

examples/mistral-vibe/skills/openlore-analyze-codebase/SKILL.md · 100 lines

How it starts

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

openlore: Analyze Codebase

When to use this skill

Trigger this skill whenever the user asks to analyze a codebase with openlore, with phrasings like:

"analyze my project / my code"
"give me a code quality report"
"what are the structural issues in my codebase"
"find duplicates in my code"
explicit command /openlore-analyze-codebase

This skill is read-only — it modifies no files. It produces a report and suggests next steps.

Step 1 — Confirm the project directory

Ask the user which project to analyze, or confirm the current workspace root.

Which project directory should I analyze?
Options: current workspace root | enter a different path

Step 2 — Run static analysis

Call the openlore MCP tool analyze_codebase with {"directory": "$DIRECTORY"}.

Step 3 — Summarize the results

Present a concise summary:

Project type and detected frameworks
File count, function count, internal call count
Top 5 refactoring issues (function name, file, issue type, priority score)
Detected domains

Also report stack inventory (read directly from .openlore/analysis/ — no extra MCP call needed):

HTTP routes: N routes across M files — if route-inventory.json exists
ORM tables: N tables — if schema-inventory.json exists
Env vars: N total, X required without default — if env-inventory.json exists
UI components: N components — if ui-inventory.json exists

If none of these files exist, skip this section and suggest running openlore analyze --force.

Step 4 — Show the call graph

Call the openlore MCP tool get_call_graph with {"directory": "$DIRECTORY"}.

Highlight:

Hub functions (fanIn ≥ 8) — over-solicited functions, high coupling risk
Layer violations detected (e.g. a UI layer calling the database directly)

Step 5 — Show duplicate code report

Call the openlore MCP tool get_duplicate_report with {"directory": "$DIRECTORY"}.

Present a concise summary:

Overall duplication ratio (e.g. "12% of functions are duplicated")
Top 3 clone groups sorted by impact (instances × line count):
- Clone type (exact / structural / near) and similarity score
- List of instances (file + function name + line range)
If no duplicates found, note this as a positive signal

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

1mo ago First seen · 100 lines · 48 tokens per session scan A 88ded8bbf915

Subscribe to this mod's changes

openlore-analyze-codebase is a skill published in the GitHub repository clay-good/OpenLore (341 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 925 once invoked, about $0.0002 per session on Opus 5.5. 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.

Debugging adr agentic-workflows ai-agents developer-tools software-architecture static-analysis

health-check

Get an overall Python code quality health score using pyscn. Use when user asks how healthy or good the code is, wants a quality overview, a grade, a summary of technical debt, or a before/after quality comparison.

ludo-technologies/pyscn · 49 tokens

agenticx-agent-obs

Configure AgenticX observability (Traces, Observations, Sessions, Token & latency metrics) for Near desktop, Python/TypeScript/Go agents, LangChain/LangGraph, and OpenAI-compatible apps, or diagnose failed traces and slow spans. Use when the user asks to enable trace reporting, connect AgenticX observability, inspect…

DemonDamon/AgenticX · 89 tokens

openlore-analyze-codebase