What is mcp-geo-repo-extent-complexity?

A report-making skill for measuring a repository’s size and functional complexity. A repository is a project’s source-code collection; the report separates committed files from other workspace files and identifies risky hotspots.

Use it to produce Markdown and optional JSON reports covering tracked files, workspace files, complexity, recent change activity, and the highest-risk areas.

It avoids counting generated files as real project work and shows where complexity and recent changes may create maintenance risk.

mcp-geo-repo-extent-complexity — Skill for Claude Code and Codex by ch

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/chris-page-gov/mcp-geo

agentmods

npx agentmods add skills/chris-page-gov/mcp-geo/mcp-geo-repo-extent-complexity

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/chris-page-gov/mcp-geo/mcp-geo-repo-extent-complexity/github.svg)](https://agentmods.dev/skills/chris-page-gov/mcp-geo/mcp-geo-repo-extent-complexity)

Your own site

<a href="https://agentmods.dev/skills/chris-page-gov/mcp-geo/mcp-geo-repo-extent-complexity"><img src="https://agentmods.dev/badge/skills/chris-page-gov/mcp-geo/mcp-geo-repo-extent-complexity/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/chris-page-gov/mcp-geo/mcp-geo-repo-extent-complexity"><img src="https://agentmods.dev/badge/skills/chris-page-gov/mcp-geo/mcp-geo-repo-extent-complexity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 592 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.00046	$0.00592
Opus 5	$0.00023	$0.00296
Sonnet 5	$0.00009	$0.00118
Haiku 4.5	$0.00005	$0.00059

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

Security

Grade A, and why

mcp-geo-repo-extent-complexity 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 12d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/run_report.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/mcp-geo-repo-extent-complexity/SKILL.md · 77 lines

How it starts

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

MCP Geo Repo Extent and Complexity

Use this skill when you need a reliable complexity/extent snapshot for this repo, including mixed content and non-git files, while avoiding inflation from generated outputs.

Why this skill

Produces a dual-scope view:
- git_tracked (what is committed)
- workspace (tracked + untracked non-ignored)
Focuses on functional complexity, not artifact volume.
Excludes known generated/output paths by default and honors Linguist attributes (linguist-generated, linguist-vendored) when available.
Surfaces change-risk hotspots using complexity x churn.

Inputs

Local repository checkout.
Optional GitHub access via gh CLI for additional stats.

Outputs

Markdown report in docs/reports/.
Manager-facing report card in docs/reports/ with plain-English terminology, source/basis notes, and practical implications.
Optional JSON payload for dashboards/time-series tracking.

Runbook

Generate report (recommended):

python3 scripts/repo_extent_complexity_report.py \
  --scope both \
  --lookback-days 180 \
  --top-hotspots 20 \
  --output docs/reports/repo_extent_complexity_$(date -u +%F).md \
  --json-output docs/reports/repo_extent_complexity_$(date -u +%F).json \
  --manager-output docs/reports/repo_extent_complexity_report_card_$(date -u +%F).md

Include GitHub stats when gh is authenticated:

python3 scripts/repo_extent_complexity_report.py \
  --scope both \
  --include-github

Add custom exclusions when needed (for generated assets):

python3 scripts/repo_extent_complexity_report.py \
  --exclude-glob "data/exports/**" \
  --exclude-glob "playground/screenshots/**"

Interpretation guide

Use the manager report card for non-technical stakeholders; it explains each metric in plain English with practical operational impact.
Prioritize hotspots with both high complexity_points and high recent churn.
Use workspace scope to catch high-risk uncommitted/untracked code.
Use git_tracked scope for release and governance reporting.
Treat docs/data growth as context, not implementation complexity.

Read the full file on GitHub · 77 lines

Files

What ships with it

2 files 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.

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.

12d ago First seen · 77 lines · 46 tokens per session scan A 6f066c5279b0

Subscribe to this mod's changes

mcp-geo-repo-extent-complexity is a skill published in the GitHub repository chris-page-gov/mcp-geo (3 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 592 once invoked, about $0.0002 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.

Analytics and metrics

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens