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/Cyvid7-Darus10/claude-code-configWrote 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/cyvid7-darus10/claude-code-config/ponytail-review)<a href="https://agentmods.dev/commands/cyvid7-darus10/claude-code-config/ponytail-review"><img src="https://agentmods.dev/badge/commands/cyvid7-darus10/claude-code-config/ponytail-review/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/cyvid7-darus10/claude-code-config/ponytail-review"><img src="https://agentmods.dev/badge/commands/cyvid7-darus10/claude-code-config/ponytail-review.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.00011 | $0.00113 |
| Opus 5 | $0.00005 | $0.00056 |
| Sonnet 5 | $0.00002 | $0.00023 |
| Haiku 4.5 | $0.00001 | $0.00011 |
Grade A, and why
ponytail-review 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 9d 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.
This is a copy
100% identical to ponytail-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Review the current code changes for over-engineering only, not correctness. One line per finding: L: . . Tags: delete (dead code/speculative feature), stdlib (reinvented standard library), native (dependency doing what the platform does), yagni (abstraction with one implementation), shrink (same logic, fewer lines). End with the net lines removable. If nothing to cut: 'Lean already. Ship.'
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.
- 9d ago First seen · 6 lines · 11 tokens per session scan A ff09bd42b1d2
ponytail-review is a command published in the GitHub repository Cyvid7-Darus10/claude-code-config (2 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 113 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ponytail-review, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
code-review
A review of uncommitted code changes for security problems, quality issues, and common maintenance concerns. A commit is a saved change in a version-control system such as Git.
sonarqube
Analyze SonarCloud quality issues for a specific PR.
review-pr
Perform a comprehensive code review of a pull request.
pr
Analyze changes, detect scope issues, and create a well-structured PR.
refactor
Analyze code for SOLID violations and suggest targeted improvements.
handoff-verify
A pre-merge review command that sends a code change to several reviewers, then rechecks serious findings. Pre-merge means before the change is added to the main codebase.