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/setup)<a href="https://agentmods.dev/commands/ccplugins/awesome-claude-code-plugins/setup"><img src="https://agentmods.dev/badge/commands/ccplugins/awesome-claude-code-plugins/setup/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/setup"><img src="https://agentmods.dev/badge/commands/ccplugins/awesome-claude-code-plugins/setup.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.00014 | $0.00363 |
| Opus 5.5 | $0.00006 | $0.00145 |
| Sonnet 5.5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
setup 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
1 near-identical copy found in the catalogue:
- setup — 100% identical, 0 lines differ
What it actually says
Check each prerequisite and report it as ✅ or ❌ with the exact fix command:
- Codex CLI installed —
codex --version(fix:npm i -g @openai/codex) - Codex authenticated —
codex login statusor the equivalent for the installed version (fix:codex login) - Inside a git repo —
git rev-parse --is-inside-work-tree. Distinguish the two failure modes: git not installed (fix:xcode-select --installon macOS,apt install git/winget install Git.Gitelsewhere) vs. not a repository (fix:git init— ClauDex reviews diffs, so it needs one) - Optional: the official Codex plugin for
/codex:*commands (/plugin marketplace add openai/codex-plugin-cc, then/plugin install codex@openai-codex)
When everything passes, reply:
"ClauDex is ready. Claude writes, Codex reviews, you ship. 🧡🖤
First time? Run /claudex:demo — two minutes, zero risk: watch the two
models argue over planted bugs before you point them at real code."
If the Codex CLI or its login is missing, end with:
"It takes two to ClauDex. 🧡 Claude is here — 🖤 Codex is not. Run the fix
commands above, then /claudex:setup again for the duet."
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 · 26 lines · 14 tokens per session scan A c57f2e6a7ac1
setup is a command published in the GitHub repository ccplugins/awesome-claude-code-plugins (978 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 363 once invoked, about $0.0001 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-09-03.
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.
github-issue-fix
This is a detailed way you can analyze the GitHub issues and let Claude handle them in best possible way.
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.
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.
create-worktrees
Creates git worktrees for all open PRs or specific branches, handling branches with slashes, cleaning up stale worktrees, and supporting custom branch creation for development.