codebase-inspection

codebase-inspection is a skill for Claude Code, Codex from AtlasOmnia/hermes-custom-pack. It costs 24 tokens per session (969 once invoked), scanned A, a copy of codebase-inspection, MIT.

A repository analysis workflow that uses pygount to count lines of code, files, programming languages, and comments. A repository is a project's stored source files and history.

In plain words
What is it for?
Use it to measure a repository, compare language usage, count files, or calculate code-to-comment ratios. It is suited to questions such as how large a project is.
Why use it?
It provides a consistent view of a codebase's size and composition while excluding dependencies and generated build files. This avoids misleading totals and unnecessarily slow scans.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to measure a repository, compare language usage, count files, or calculate code-to-comment ratios. It is suited to questions such as how large a project is.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/atlasomnia/hermes-custom-pack/codebase-inspection
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 AtlasOmnia/hermes-custom-pack --skill codebase-inspection
Clone the repo
git clone --depth 1 https://github.com/AtlasOmnia/hermes-custom-pack

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.

agentmods badge for codebase-inspection

README.md
[![agentmods](https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/codebase-inspection/github.svg)](https://agentmods.dev/skills/atlasomnia/hermes-custom-pack/codebase-inspection)
Your own site
<a href="https://agentmods.dev/skills/atlasomnia/hermes-custom-pack/codebase-inspection"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/codebase-inspection/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 codebase-inspection

Your own site · 80×15
<a href="https://agentmods.dev/skills/atlasomnia/hermes-custom-pack/codebase-inspection"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/codebase-inspection.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 969 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 100% copy Near-identical to another mod 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.00024 $0.00969
Opus 5.5 $0.00010 $0.00388
Sonnet 5.5 $0.00005 $0.00194
Haiku 4.5 $0.00002 $0.00097

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

Security

Grade A, and why

codebase-inspection 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.

Origin

This is a copy

100% identical to codebase-inspection — 28 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/codebase-inspection/SKILL.md · 127 lines

How it starts

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

Codebase Inspection with pygount

Analyze repositories for lines of code, language breakdown, file counts, and code-vs-comment ratios using pygount.

When to Use

  • User asks for LOC (lines of code) count
  • User wants a language breakdown of a repo
  • User asks about codebase size or composition
  • User wants code-vs-comment ratios
  • General "how big is this repo" questions

Prerequisites

pip install --break-system-packages pygount 2>/dev/null || pip install pygount

1. Basic Summary (Most Common)

Get a full language breakdown with file counts, code lines, and comment lines:

cd /path/to/repo
pygount --format=summary \
 --folders-to-skip=".git,node_modules,venv,.venv,__pycache__,.cache,dist,build,.next,.tox,.eggs,*.egg-info" \
 .

IMPORTANT: Always use --folders-to-skip to exclude dependency/build directories, otherwise pygount will crawl them and take a very long time or hang.

2. Common Folder Exclusions

Adjust based on the project type:

# Python projects
--folders-to-skip=".git,venv,.venv,__pycache__,.cache,dist,build,.tox,.eggs,.mypy_cache"

# JavaScript/TypeScript projects
--folders-to-skip=".git,node_modules,dist,build,.next,.cache,.turbo,coverage"

# General catch-all
--folders-to-skip=".git,node_modules,venv,.venv,__pycache__,.cache,dist,build,.next,.tox,vendor,third_party"

3. Filter by Specific Language

# Only count Python files
pygount --suffix=py --format=summary .

# Only count Python and YAML
pygount --suffix=py,yaml,yml --format=summary .

4. Detailed File-by-File Output

# Default format shows per-file breakdown
pygount --folders-to-skip=".git,node_modules,venv" .

# Sort by code lines (pipe through sort)
pygount --folders-to-skip=".git,node_modules,venv" . | sort -t$'\t' -k1 -nr | head -20

5. Output Formats

# Summary table (default recommendation)
pygount --format=summary .

# JSON output for programmatic use
pygount --format=json .

# Pipe-friendly: Language, file count, code, docs, empty, string
pygount --format=summary . 2>/dev/null

Read the full file on GitHub · 127 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. 1mo ago First seen · 127 lines · 24 tokens per session scan A 96455878d6e9

Subscribe to this mod's changes

codebase-inspection is a skill published in the GitHub repository AtlasOmnia/hermes-custom-pack (70 stars, last pushed 7d ago), licensed MIT. It adds 24 tokens to every session and 969 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to codebase-inspection, differing in 28 lines, and is treated as a copy.