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.
git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWrote 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/commands/ccplugins/awesome-claude-code-plugins/analyze-codebase)<a href="https://agentmods.dev/commands/ccplugins/awesome-claude-code-plugins/analyze-codebase"><img src="https://agentmods.dev/badge/commands/ccplugins/awesome-claude-code-plugins/analyze-codebase/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/commands/ccplugins/awesome-claude-code-plugins/analyze-codebase"><img src="https://agentmods.dev/badge/commands/ccplugins/awesome-claude-code-plugins/analyze-codebase.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.00009 | $0.01800 |
| Opus 5.5 | $0.00004 | $0.00720 |
| Sonnet 5.5 | $0.00002 | $0.00360 |
| Haiku 4.5 | $0.00001 | $0.00180 |
Grade A, and why
analyze-codebase 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- analyze-codebase — 100% identical, 0 lines differ
- analyze-codebase — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprehensive Codebase Analysis
Project Discovery Phase
Directory Structure
!find . -type d -not -path "./node_modules/*" -not -path "./.git/*" -not -path "./dist/*" -not -path "./build/*" -not -path "./.next/*" -not -path "./coverage/*" | sort
Complete File Tree
!tree -a -I 'node_modules|.git|dist|build|.next|coverage|*.log' -L 4
File Count and Size Analysis
- Total files: !
find . -type f -not -path "./node_modules/*" -not -path "./.git/*" | wc -l - Code files: !
find . -name "*.js" -o -name "*.ts" -o -name "*.jsx" -o -name "*.tsx" -o -name "*.py" -o -name "*.java" -o -name "*.php" -o -name "*.rb" -o -name "*.go" -o -name "*.rs" -o -name "*.cpp" -o -name "*.c" | grep -v node_modules | wc -l - Project size: !
du -sh . --exclude=node_modules --exclude=.git --exclude=dist --exclude=build
Configuration Files Analysis
Package Management
- Package.json: @package.json
- Package-lock.json exists: !
ls package-lock.json 2>/dev/null || echo "Not found" - Yarn.lock exists: !
ls yarn.lock 2>/dev/null || echo "Not found" - Requirements.txt: @requirements.txt
- Gemfile: @Gemfile
- Cargo.toml: @Cargo.toml
- Go.mod: @go.mod
- Composer.json: @composer.json
Build & Dev Tools
- Webpack config: @webpack.config.js
- Vite config: @vite.config.js
- Rollup config: @rollup.config.js
- Babel config: @.babelrc
- ESLint config: @.eslintrc.js
- Prettier config: @.prettierrc
- TypeScript config: @tsconfig.json
- Tailwind config: @tailwind.config.js
- Next.js config: @next.config.js
Environment & Docker
- .env files: !
find . -name ".env*" -type f - Docker files: !
find . -name "Dockerfile*" -o -name "docker-compose*" - Kubernetes files: !
find . -name "*.yaml" -o -name "*.yml" | grep -E "(k8s|kubernetes|deployment|service)"
CI/CD Configuration
- GitHub Actions: !
find .github -name "*.yml" -o -name "*.yaml" 2>/dev/null || echo "No GitHub Actions" - GitLab CI: @.gitlab-ci.yml
- Travis CI: @.travis.yml
- Circle CI: @.circleci/config.yml
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.
- 1mo ago First seen · 165 lines · 9 tokens per session scan A 879714da8bd2
analyze-codebase is a command published in the GitHub repository ccplugins/awesome-claude-code-plugins (974 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 1,800 once invoked, about $0.0000 per session on Opus 5.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-30.
Other commands, from other repositories
create-pull-request
Provides comprehensive PR creation guidance with GitHub CLI, enforcing title conventions, following template structure, and offering concrete command examples with best practices.
pr-issue-resolve
Follow these steps to analyze suggested changes (e.g., review comments, inline suggestions, or requested modifications) in a GitHub Pull Request (PR) and resolve them efficiently. The goal is to review, understand, plan fixes, apply changes, test, and update the PR while maintaining code quality and collaboration.
openapi-expert
Use this agent when you need to update, synchronize, or validate the OpenAPI specification (openapi.yml) against the actual REST API implementation. This includes adding new endpoints, updating request/response schemas, fixing discrepancies between the spec and code, or ensuring complete API documentation coverage.
pr-review
Reviews pull request changes to provide feedback, check for issues, and suggest improvements before merging into the main codebase.
create-pr
Streamlines pull request creation by handling the entire workflow: creating a new branch, committing changes, formatting modified files with Biome, and submitting the PR.
husky
Sets up and manages Husky Git hooks by configuring pre-commit hooks, establishing commit message standards, integrating with linting tools, and ensuring code quality on commits.