project-analysis

project-analysis is a skill for Codex from Bamzzo/project-analysis-skill. It costs 87 tokens per session (2,293 once invoked), scanned A, original, MIT.

A process for building a clear map of an unfamiliar or complicated software project. It examines the project's purpose, structure, main code paths, dependencies, and risks.

In plain words
What is it for?
Use it when onboarding to a repository, reverse-engineering its architecture, documenting it, auditing it, evaluating risks, or planning substantial changes.
Why use it?
It reduces the time spent guessing how a large, old, messy, or multi-package codebase works. It also makes conclusions and remaining uncertainties explicit.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it when onboarding to a repository, reverse-engineering its architecture, documenting it, auditing it, evaluating risks, or planning substantial changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bamzzo/project-analysis-skill/project-analysis
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 Bamzzo/project-analysis-skill --skill project-analysis
Clone the repo
git clone --depth 1 https://github.com/Bamzzo/project-analysis-skill

Made for: 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.

agentmods badge for project-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/bamzzo/project-analysis-skill/project-analysis/github.svg)](https://agentmods.dev/skills/bamzzo/project-analysis-skill/project-analysis)
Your own site
<a href="https://agentmods.dev/skills/bamzzo/project-analysis-skill/project-analysis"><img src="https://agentmods.dev/badge/skills/bamzzo/project-analysis-skill/project-analysis/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 project-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/bamzzo/project-analysis-skill/project-analysis"><img src="https://agentmods.dev/badge/skills/bamzzo/project-analysis-skill/project-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,293 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00087 $0.02293
Opus 5.5 $0.00035 $0.00917
Sonnet 5.5 $0.00017 $0.00459
Haiku 4.5 $0.00009 $0.00229

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

Security

Grade A, and why

project-analysis 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 2mo 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.

project-analysis/SKILL.md · 177 lines

How it starts

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

Project Analysis

Use this skill to turn an unfamiliar or messy project into a clear, actionable map. The goal is not only to summarize files, but to explain how the project works, where its core paths are, what can break, how to verify it, and what to do next.

Operating Principles

  • Inspect before concluding. Distinguish code facts, documentation facts, runtime facts, inferences, and open questions.
  • Prefer the project's real structure over generic architecture claims.
  • Find the main path first: input -> dispatch -> core logic -> external dependency -> state/output.
  • Keep uncertainty visible. Say "inferred from" when not verified by execution.
  • Tie important conclusions to evidence: file paths, commands, test output, configs, or docs.
  • Produce action-oriented output: what to read, run, test, fix, or avoid next.
  • Do not expose secrets. If scanning configs, mention secret presence generically and avoid printing values.
  • Avoid exhaustive file-by-file summaries. Explain the system by role, flow, boundary, and risk.

Choose Depth

If the user does not specify depth, use standard.

For very large repositories, start with the surface map even when the requested depth is deep or audit.

Depth Inspect Execute Output emphasis Required evidence
quick top-level docs, manifests, scripts, major directories read-only discovery only what it is, likely stack, key files, obvious risks, next commands files/commands inspected and major unknowns
standard docs, manifests, configs, entrypoints, core modules, tests/CI safe read-only commands; run lightweight verification only when clearly appropriate architecture map, startup path, main flow, verification path, next actions file paths for main claims and commands actually run
deep standard scope plus 1-3 traced high-value flows and relevant tests/contracts targeted tests/build/typecheck or dry runs when safe flow traces, state/contracts, failure modes, missing coverage file/line evidence for traced paths and verification limits
audit broad risk surface: config, auth, state, side effects, CI/CD, dependencies, tests validation, dry-run, read-only, or explicitly safe commands only evidence ledger, risk register, readiness judgment, prioritized remediation evidence for every major risk or explicit "Open" label

Read the full file on GitHub · 177 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. 2mo ago First seen · 177 lines · 87 tokens per session scan A beb69e71f971

Subscribe to this mod's changes

project-analysis is a skill published in the GitHub repository Bamzzo/project-analysis-skill (31 stars, last pushed 5mo ago), licensed MIT. It adds 87 tokens to every session and 2,293 once invoked, about $0.0003 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.

Related

project-analysis compared with skills from other repositories

project-analysis next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
project-analysisBamzzo/project-analysis-skillSkill315mo agoMITA87Codex
imagegenopenai/codexSkill135ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill100ktodayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k5d agoMITA200Claude Code, Codex
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
systematic-debuggingobra/superpowersSkill316k8d agoMITA21Claude Code