What is project-summary?

A command that produces an overview of a software project, including its structure, technologies, architecture, and basic statistics.

Use it to identify the project type, programming language, framework, dependencies, entry points, source and test folders, and major components.

It saves time when you need to understand an unfamiliar codebase before making changes.

project-summary — Command for Claude Code by nolabs-ai

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.

Clone the repo

git clone --depth 1 https://github.com/nolabs-ai/claude-extensions

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/commands/nolabs-ai/claude-extensions/project-summary.svg)](https://agentmods.dev/commands/nolabs-ai/claude-extensions/project-summary)

Your own site

<a href="https://agentmods.dev/commands/nolabs-ai/claude-extensions/project-summary"><img src="https://agentmods.dev/badge/commands/nolabs-ai/claude-extensions/project-summary.svg" alt="Measured on agentmods" height="20"></a>

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 537 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.00008	$0.00537
Opus 5	$0.00004	$0.00269
Sonnet 5	$0.00002	$0.00107
Haiku 4.5	$0.00001	$0.00054

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

Security

Grade A, and why

project-summary 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 7d 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.

commands/project-summary.md · 109 lines

How it starts

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

Project Summary

Generate an overview of the current project structure, technologies, and key components.

Process

Identify Project Type
- Check for package.json, pyproject.toml, go.mod, Cargo.toml
- Identify primary language and framework
Analyze Structure
- Map directory structure
- Identify source, test, and config directories
- Find entry points
Detect Technologies
- Parse dependency files
- Identify frameworks and libraries
- Note development tools
Summarize Architecture
- Identify architectural patterns
- Map key components
- Note integrations

Output Format

Project: [Name]

Type: [Web App / CLI / Library / API / etc.] Language: [Primary language] Framework: [If applicable]

Quick Stats

Files: X
Lines of Code: ~X
Dependencies: X production, X development

Directory Structure

project/
├── src/           # Source code
├── tests/         # Test files
├── docs/          # Documentation
└── ...

Technology Stack

Runtime:

Node.js / Python / Go / etc.

Framework:

Express / Django / Gin / etc.

Key Libraries:

Library 1 - purpose
Library 2 - purpose

Development:

TypeScript / Jest / ESLint / etc.

Architecture Overview

[Description of the project's architecture pattern]

Key Components:

Component 1: Description
Component 2: Description

Data Flow: [Brief description of how data flows through the system]

Entry Points

src/index.ts - Main application entry
src/cli.ts - CLI interface

Configuration

.env - Environment variables
config/ - Configuration files

Scripts

Command	Description
`npm start`	Run the application
`npm test`	Run tests
`npm run build`	Build for production

Arguments

brief - One-paragraph summary
detailed - Full analysis with code examples
No argument - Standard overview

Guidelines

Focus on what a new developer needs to know
Highlight architectural decisions
Note any unusual patterns
Identify potential areas of complexity

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

7d ago First seen · 109 lines · 8 tokens per session scan A b58db8b6adc3

Subscribe to this mod's changes

project-summary is a command published in the GitHub repository nolabs-ai/claude-extensions (5 stars, last pushed 8mo ago), licensed MIT. It adds 8 tokens to every session and 537 once invoked, about $0.0000 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.

project-summary