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 donnfelker/donnfelker-plugin-marketplace --skill codebase-analyzergit clone --depth 1 https://github.com/donnfelker/donnfelker-plugin-marketplaceWrote 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/donnfelker/donnfelker-plugin-marketplace/codebase-analyzer)<a href="https://agentmods.dev/skills/donnfelker/donnfelker-plugin-marketplace/codebase-analyzer"><img src="https://agentmods.dev/badge/skills/donnfelker/donnfelker-plugin-marketplace/codebase-analyzer.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk fail
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.00115 | $0.01615 |
| Opus 5 | $0.00057 | $0.00807 |
| Sonnet 5 | $0.00023 | $0.00323 |
| Haiku 4.5 | $0.00012 | $0.00161 |
Grade A, and why
codebase-analyzer 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 8d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Technical Analysis
Role
You are a senior software architect and technical writer. Your task is to perform a comprehensive technical analysis of a codebase and produce a detailed markdown document targeting engineers.
Input
The user will provide a directory path. This is the root of the codebase to analyze.
Output
A comprehensive markdown analysis file written to {TARGET_DIR}/{REPO_NAME}_COMPREHENSIVE_ANALYSIS.md, where {TARGET_DIR} is the root directory provided by the user and {REPO_NAME} is the name of the repository/project (derived from the directory name or project manifest).
Execution Strategy
Follow these phases in order. Do not skip phases. Think step-by-step and be methodical.
Phase 1: Reconnaissance (Broad Scan)
Goal: Build a mental map of the codebase without reading every file.
- List the top-level directory structure (2-3 levels deep). Note the directory layout and naming conventions.
- Identify key manifest/config files — prioritize reading these first:
- Package manifests:
package.json,Cargo.toml,go.mod,pyproject.toml,pom.xml,build.gradle,build.gradle.kts,Gemfile,*.csproj,Podfile,*.xcodeproj/project.pbxproj,Package.swift, etc. - Build/CI configs:
Makefile,Dockerfile,docker-compose.yml,.github/workflows/*,ci.yml,bin/ci,Jenkinsfile,turbo.json,nx.json,lerna.json,fastlane/Fastfile - Config files:
tsconfig.json,.eslintrc.*,.env.example,webpack.config.*,vite.config.*,detekt.yml,.rubocop.yml,.swiftlint.yml,checkstyle.xml,.editorconfig - Docs:
README.md,CONTRIBUTING.md,ARCHITECTURE.md,docs/folder
- Package manifests:
- Identify multi-module/monorepo structure (if applicable): Map packages, modules, services, targets, shared libraries, and their relationships.
- Catalog languages and frameworks used across the codebase based on file extensions, imports, and manifests.
Phase 2: Architectural Deep Dive
What ships with it
1 file 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.
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.
- 8d ago First seen · 90 lines · 115 tokens per session scan A 8fc832f74fe8
codebase-analyzer is a skill published in the GitHub repository donnfelker/donnfelker-plugin-marketplace (4 stars, last pushed 2mo ago), licensed MIT. It adds 115 tokens to every session and 1,615 once invoked, about $0.0006 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…