repo-analyze

A codebase overview tool that summarizes a repository’s files, languages, frameworks, build tools, dependencies, starting files, and README notes.

In plain words
What is it for?
Use it to identify a project’s technology stack, find likely entry points, and get a quick orientation before changing code.
Why use it?
It gives a coding agent the main project facts in one result, reducing repeated file searches when work begins in an unfamiliar repository.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add osouthgate/agent-plus
agentmods
npx agentmods add plugins/osouthgate/agent-plus/repo-analyze
Clone the repo
git clone --depth 1 https://github.com/osouthgate/agent-plus

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 1 skill cost 94 tokens a session between them.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

repo-analyze 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 2d 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.

repo-analyze/.claude-plugin/plugin.json · 14 lines

What it actually says

{
  "name": "repo-analyze",
  "description": "Cold-start codebase orientation in one call. Returns a structured map of a repo — file tree (capped), language mix, framework + build-tool detection, top-level deps, entrypoints, README highlights — so an agent doesn't burn 60+ Read/Glob/Grep calls re-mining the same facts on every fresh session.",
  "version": "0.3.0",
  "author": {
    "name": "Oliver Southgate",
    "url": "https://github.com/osouthgate"
  },
  "homepage": "https://github.com/osouthgate/agent-plus",
  "repository": "https://github.com/osouthgate/agent-plus",
  "license": "MIT",
  "keywords": ["codebase", "analysis", "orientation", "cold-start", "agent-plus", "repo-overview"]
}
Contents

What it installs

The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 94 tokens a session between them. Each is measured on its own page, and each can be installed alone.

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. 2d ago First seen · 14 lines scan A 8da6022c56e6

Subscribe to this mod's changes

repo-analyze is a plugin published in the GitHub repository osouthgate/agent-plus (4 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.