A code-structure analysis tool that maps modules, symbols, routes, storage, and their relationships across a codebase. It can compare the structure before and after a change.

Use it to trace dependencies, estimate change impact, find unused code, inspect package boundaries and structural performance risks, and run a quality check after structural edits.

It reduces the need to reconstruct architecture with broad searches and helps reveal which parts of a system may be affected by a change.

enola — Skill for Claude Code by enola-labs

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 enola-labs/enola --skill enola

Clone the repo

git clone --depth 1 https://github.com/enola-labs/enola

Made for: Claude Code.

Or install enola, the plugin that ships this one along with the rest of its 2 skills, 2 hooks.

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/enola-labs/enola/enola/github.svg)](https://agentmods.dev/skills/enola-labs/enola/enola)

Your own site

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

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

When invoked 511 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.

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.00034	$0.00511
Opus 5.5	$0.00014	$0.00204
Sonnet 5.5	$0.00007	$0.00102
Haiku 4.5	$0.00003	$0.00051

Measured 16d ago against content hash 510753920fc2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

enola 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 16d 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.

plugins/enola/skills/enola/SKILL.md · 55 lines

How it starts

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

Enola — architecture before and after a change

Enola serves a deterministic structural map over MCP: modules, symbols, routes, storage, and the relationships between them. Use its tools for architectural questions instead of reconstructing the same information through broad file searches.

Before changing code whose blast radius is unclear:

Use impact_analysis to find transitive dependents.
Use explore, traverse, or find_path to understand how code is wired.
Use set_baseline once, before editing, if the session hook has not pinned one.
Use find_orphans before adding more callers to apparently unused symbols.
Use package_metrics for package-boundary decisions.
Use analyze_performance for structural performance risks.

After a structural change, use generate_snapshot and diff_snapshot to inspect what moved: findings introduced or resolved, coupling added, and symbols added or removed.

The gate: `enola check`

enola check is an important part of the workflow. The MCP tools help an agent understand and inspect a change; enola check is the CLI and CI quality gate with a stable exit-code contract. Run it after making structural changes and before reporting the work complete:

enola check

A bare enola check reports the delta but intentionally fails nothing. A repository that wants enforcement must name its policy, for example:

enola check --fail-on=layers

Do not add or change enforcement flags on the user's behalf. Use the policy already declared by the repository or ask the user which rules should gate the build.

Enola reports movement from a pinned baseline, not every existing problem. A finding that no policy enforced is evidence to show the user, not authorization to revert or refactor unrelated code. Do not describe a change as architecturally clean when the check could not run or its baseline was not comparable.

If the enola executable is missing, explain that this plugin requires the Enola CLI on PATH, point the user to the repository installation instructions, and verify the installation with enola doctor. Never install or upgrade the executable without the user's approval.

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

16d ago First seen · 55 lines · 34 tokens per session scan A 510753920fc2

Subscribe to this mod's changes

enola is a skill published in the GitHub repository enola-labs/enola (257 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 511 once invoked, about $0.0001 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-09-22.

Code review Debugging ai-coding architecture-analysis code-intelligence developer-tools impact-analysis static-analysis

systemic-issue-triage

Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.

Gentleman-Programming/gentle-ai · 57 tokens

issue-root-resolution

Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.

Gentleman-Programming/gentle-ai · 45 tokens

rdd-defect-workflow

Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.

Gentleman-Programming/gentle-ai · 41 tokens

lsp-inspect

Full code quality audit for a file, package, or directory. Supports batch mode (directory walk with --top ranking), comparison mode (--diff for branch-only issues), severity calibration by blast radius, fix suggestions, and confidence tiers. Applies a check taxonomy (dead symbols, silent failures, error wrapping…

blackwell-systems/agent-lsp · 126 tokens

lsp-dead-code

Enumerate exported symbols in a file and surface those with zero references across the workspace. Use when auditing for dead code, cleaning up APIs, or checking which exports are safe to remove.

blackwell-systems/agent-lsp · 43 tokens

lsp-impact

Blast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count before you change it. Use when refactoring, deleting, or changing the signature of any function, type, or method. Also accepts a file path to surface all exported-symbol impact in one shot.

blackwell-systems/agent-lsp · 67 tokens