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 ryo-ebata/cc-audit --skill cleangit clone --depth 1 https://github.com/ryo-ebata/cc-auditWrote 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/ryo-ebata/cc-audit/clean)<a href="https://agentmods.dev/skills/ryo-ebata/cc-audit/clean"><img src="https://agentmods.dev/badge/skills/ryo-ebata/cc-audit/clean/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/skills/ryo-ebata/cc-audit/clean"><img src="https://agentmods.dev/badge/skills/ryo-ebata/cc-audit/clean.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00013 | $0.00115 |
| Opus 5.5 | $0.00005 | $0.00046 |
| Sonnet 5.5 | $0.00003 | $0.00023 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
code-review-helper 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.
What it actually says
Code Review Helper
This skill assists with code review by analyzing files and providing feedback.
Usage
- Point to the file you want to review
- The skill will analyze code quality
- Suggestions will be provided
Example
Please review src/main.rs for potential improvements
Notes
- This skill only reads and writes files
- No network access required
- No system commands executed
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 · 27 lines · 13 tokens per session scan A bcae7b01ceb2
code-review-helper is a skill published in the GitHub repository ryo-ebata/cc-audit (26 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 115 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-08-30.
Other skills, from other repositories
audit
Deep code audit — security, tests, architecture, performance, stack-specific checks.
factorize
Scan the project for duplication and factorization opportunities.
review
Auto-review changes before committing — stack-aware checklist.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
review
Diff-scoped correctness review that reads the codebase around the change — callers, contracts, and invariants — and returns line-anchored findings ranked by severity with confidence, then a merge-risk verdict. Use for reviewing a PR, diff, or named change set. Not for style review, approvals-as-rubber-stamp, or…
cw-slice
Use before writing code for any Codewhale feature, upgrade, or refactor: find the existing owner of the behavior, bound the change to one reviewable slice, and fix the evidence bar before you start.