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 agentmods add commands/ccplugins/awesome-claude-code-plugins/statsgit 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/stats)<a href="https://agentmods.dev/commands/ccplugins/awesome-claude-code-plugins/stats"><img src="https://agentmods.dev/badge/commands/ccplugins/awesome-claude-code-plugins/stats.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00455 |
| Opus 5 | $0.00008 | $0.00228 |
| Sonnet 5 | $0.00003 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
stats 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 yesterday.
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:
- stats — 100% identical, 0 lines differ
What it actually says
You are running ClauDex stats — a read-only tally of the duet's history in this repository. No review happens here and no Codex call is made, so this command never signs: the 🧡🖤 line is earned by cross-review only, and counting past reviews is not one.
- Find the ledger. Confirm you are in a git repo
(
git rev-parse --git-dir); the ledger lives at<git-dir>/claudex/stats.jsonl. If the repo, the file, or its contents are missing, say so plainly: runs are recorded from ClauDex v0.6.0 onward, so older duets are invisible — "Run/claudex:verdictor/claudex <task>and come back; every run writes one line." - Tally. Parse each JSON line, skipping (and counting) malformed ones:
- Runs per command, and outcomes: signed / interrupted / deadlocked / nothing-to-review.
- The headline — agreement rate across
verdictruns:both / (both + claude_only + codex_only). - Verdict rulings: SHIP vs FIX FIRST vs REDESIGN.
- Loop runs: average rounds to consensus, and Codex's hit rate —
fixed / (fixed + rejected)(how often its findings held up). - Debates: CONSENSUS vs SPLIT.
- Interruption rate overall (the duet's reliability in this repo).
- Report. A compact table, then one headline sentence, e.g.: "Across 12 reviews the models agreed on 41% of findings — and every disagreement was a place a human looked." If there are fewer than 5 runs, say the numbers are anecdotes, not statistics, and skip the percentage framing.
- End without the sign-off line — this command neither builds, reviews, nor argues.
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.
- yesterday First seen · 33 lines · 16 tokens per session scan A 0e8212815426
stats is a command published in the GitHub repository ccplugins/awesome-claude-code-plugins (931 stars, last pushed 23d ago), licensed Apache-2.0. It adds 16 tokens to every session and 455 once invoked, about $0.0001 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-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.
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.
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.
pr-review
Reviews pull request changes to provide feedback, check for issues, and suggest improvements before merging into the main codebase.