A code-analysis workflow that reconstructs a project’s architecture from its source code. It records components, dependencies, risks, code smells, dead code, coupling, and missing tests in analysis.md.

Use it to inspect entry points and modules, recover interfaces and dependencies, identify quality risks, and capture findings for later work.

It provides a documented view of how the code really works, including maintenance problems that may not be visible from requirements alone.

How MaximilianMayr94/skills configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to MaximilianMayr94/skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/MaximilianMayr94/skills/main/.github/skills/analyse/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/MaximilianMayr94/skills

Made for: Claude Code.

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

Your own site

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

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

When invoked 361 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.00015	$0.00361
Opus 5	$0.00008	$0.00180
Sonnet 5	$0.00003	$0.00072
Haiku 4.5	$0.00002	$0.00036

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

Security

Grade A, and why

analyse 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 10d 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.

.github/skills/analyse/SKILL.md · 33 lines

What it actually says

Goal

Recover the real architecture from the code that was requested by the user and capture its properties.

Phase 1 - Load

Load copilot/context.md from the target project and copilot/architecture.md if present.
Scan the requested part of the codebase: entry points, modules, dependencies.
Reconstruct architecture
Record smells, risks, dead code, coupling, missing tests.

Phase 2 - Discuss

Phase 3 - Discuss with user

Ask the user open questions. Do not ask all questions at once, but one by one, discuss each question and its answer before moving to the next one.
Every few questions (max. 5) ask the user if he wants to progress to phase 3 or if he wants to continue refining with more questions.
For each question give the user a custom answer field so he can enter something else

Phase 3 - Write analysis.md

Write copilot/analysis.md using analysis.default.md (this folder) as template.
See analysis.example.md for a filled-out example.
Structure:
- Architecture: reconstructed components, functionality and interfaces. Use diagrams/flowcharts.
- Code Quality: smells, risks, dead code, coupling, missing tests. Bullet points + concrete examples.
- Identified Gaps and Problems: gaps and contradictions in code vs. context/architecture. Bullet points + examples.

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

analysis.default.md 1.0 KB

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.

10d ago First seen · 33 lines · 15 tokens per session scan A 4c08e97e838a

Subscribe to this mod's changes

analyse is a skill published in the GitHub repository MaximilianMayr94/skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 361 once invoked, about $0.0001 per session on Opus 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-31.

Debugging

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens

skills: Skill for Claude Code