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/cassler/awesome-claude-code-setupWrote 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/cassler/awesome-claude-code-setup/pre-review-check)<a href="https://agentmods.dev/commands/cassler/awesome-claude-code-setup/pre-review-check"><img src="https://agentmods.dev/badge/commands/cassler/awesome-claude-code-setup/pre-review-check.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.1 | $0.00000 | $0.00807 |
| Opus 5 | $0.00000 | $0.00404 |
| Sonnet 5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
pre-review-check 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Review Checklist
Please help me ensure my code is ready for review.
PR/Branch: ${PR_BRANCH:-current branch} Focus areas: ${FOCUS_AREAS:-all changes}
Quality Checks
-
Find and fix debug code:
# Find TODOs that need addressing ch cq todos --with-context # Remove debug logs ch cq console-logs # Check for commented code chs find-code "^\\s*//.*\\b(console|debug|test)" -
Check code quality metrics:
# Find overly large files ch cq large-files ${MAX_LINES:-500} # Check complexity ch cq complexity ${MAX_COMPLEXITY:-10} # Look for duplicated code patterns chs find-code "$PATTERN" --count -
Security scan:
# Scan for hardcoded secrets ch cq secrets-scan # Check for sensitive data in logs chs find-code "password|token|secret|key" --exclude .env -
Verify test coverage:
# Find untested files if ! git diff --name-only origin/main...HEAD 2>/dev/null | while IFS= read -r f; do echo "Checking tests for: $f" chs find-file "*.test.*" | xargs grep -l "$(basename "$f" .js)" 2>/dev/null || echo " No tests found for $f" done; then echo "Note: Could not compare with origin/main" fi # Run tests ch ts test -
Check dependencies:
# Audit for vulnerabilities ch ts audit # Check for unused dependencies ch ts deps --check-unused -
Documentation check:
- Are new functions documented?
- Is the README updated if needed?
- Are breaking changes noted?
PR Preparation
-
Generate context for reviewers:
# Create summary ch ctx summarize > PR_CONTEXT.md # Show what changed git diff --stat origin/main...HEAD -
Check commit history:
# Review commits git log --oneline origin/main..HEAD # Consider squashing if needed -
Update PR if exists:
# Check if PR exists PR_NUMBER=$(gh pr list --head "$(git branch --show-current)" --json number -q ".[0].number") if [ -n "$PR_NUMBER" ]; then # Update PR description with context gh pr edit "$PR_NUMBER" --body "$(gh pr view "$PR_NUMBER" --json body -q .body)\n\n## Review Context\n\n$(cat PR_CONTEXT.md)" # Mark as ready if it's a draft gh pr ready "$PR_NUMBER" 2>/dev/null || echo "PR already ready for review" # Add review request if needed gh pr edit "$PR_NUMBER" --add-reviewer "${REVIEWER:-@me}" else echo "No PR found. Create one with: gh pr create" fi
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.
- 7d ago First seen · 120 lines · 0 tokens per session scan A 624d371e0ef8
pre-review-check is a command published in the GitHub repository cassler/awesome-claude-code-setup (267 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 807 tokens. 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
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
review-sdk-app
Review and validate a Claude Agent SDK application against best practices.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.