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.
npx skills add KunanonJ/ai-skills-hub --skill analyze-codebase-for-mcpgit clone --depth 1 https://github.com/KunanonJ/ai-skills-hubWrote 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.
[](https://agentmods.dev/skills/kunanonj/ai-skills-hub/analyze-codebase-for-mcp)<a href="https://agentmods.dev/skills/kunanonj/ai-skills-hub/analyze-codebase-for-mcp"><img src="https://agentmods.dev/badge/skills/kunanonj/ai-skills-hub/analyze-codebase-for-mcp/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.
<a href="https://agentmods.dev/skills/kunanonj/ai-skills-hub/analyze-codebase-for-mcp"><img src="https://agentmods.dev/badge/skills/kunanonj/ai-skills-hub/analyze-codebase-for-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00090 | $0.02403 |
| Opus 5 | $0.00045 | $0.01202 |
| Sonnet 5 | $0.00018 | $0.00481 |
| Haiku 4.5 | $0.00009 | $0.00240 |
Grade A, and why
analyze-codebase-for-mcp 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.
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.
How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Codebase for MCP
Scan codebase to discover functions, REST endpoints, CLI commands, data access patterns. Good candidates for MCP tool exposure. Produce structured tool specification document.
When Use
- Planning MCP server for existing project, need to know what to expose
- Auditing codebase before wrapping as AI-accessible tool surface
- Comparing what codebase can do versus what already exposed via MCP
- Generating tool specification document to hand off to
scaffold-mcp-server - Evaluating whether third-party library worth wrapping as MCP tools
Inputs
- Required: Path to codebase root directory
- Required: Target language(s) of codebase (e.g., TypeScript, Python, R, Go)
- Optional: Existing MCP server code to compare against (gap analysis)
- Optional: Domain focus (e.g., "data analysis", "file operations", "API integration")
- Optional: Maximum number of tools to recommend (default: 20)
Steps
Step 1: Scan Codebase Structure
1.1. Use Glob to map directory tree, focusing on source directories:
src/**/*.{ts,js,py,R,go,rs}for source files**/routes/**,**/api/**,**/controllers/**for endpoint definitions**/cli/**,**/commands/**for CLI entry points**/package.json,**/setup.py,**/DESCRIPTIONfor dependency metadata
1.2. Categorize files by role:
- Entry points: main files, route handlers, CLI commands
- Core logic: business logic functions, algorithms, data transformers
- Data access: database queries, file I/O, API clients
- Utilities: helpers, formatters, validators
1.3. Count total files, lines of code, exported symbols to gauge project size.
Got: Categorized file inventory with role annotations.
If fail: Codebase too large (>10,000 files)? Narrow scan to specific directories or modules using domain focus input. No source files found? Verify root path and language parameters.
Step 2: Identify Exposed Functions and Endpoints
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 · 210 lines · 90 tokens per session scan A 4a7c4fbfd5bf
analyze-codebase-for-mcp is a skill published in the GitHub repository KunanonJ/ai-skills-hub (5 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 2,403 once invoked, about $0.0005 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.
Other skills, from other repositories
sdd-apply
Skill "sdd-apply" from Gentleman-Programming/gentle-ai, covering execution role, language domain contract, purpose, what you receive and execution and persistence contract.
backend-api
Builds server-side endpoints and data access: REST or GraphQL routes, input validation, auth flows, queries, and error contracts, contract-first and framework-agnostic. Use when adding an endpoint or API surface, wiring login, session, token, or permission logic, or writing server-side business logic that persists…
api-verification
An API verification workflow that creates both an .http request file and a .cjs JavaScript file, then runs an automation script to test them. An API is an interface through which software exchanges requests and responses.
api-contract-architecture
An architecture guide for public APIs, including HTTP services, software-development kits, command-line tools, schemas, types, errors, pagination, filtering, and compatibility.
backend-domain-architecture
A review guide for backend and business-domain design. It examines business rules, workflows, permissions, APIs, transactions, consistency, repeated requests, compatibility, data boundaries, and service responsibilities.
distributed-systems-architecture
An architecture guide for distributed systems—software split across services that communicate over networks.