Borrowing it
Nothing to install: this file belongs to opensesh/karimo-overview. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opensesh/karimo-overview/main/.claude/commands/karimo/greptile-review.mdgit clone --depth 1 https://github.com/opensesh/karimo-overviewWrote 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/opensesh/karimo-overview/greptile-review)<a href="https://agentmods.dev/commands/opensesh/karimo-overview/greptile-review"><img src="https://agentmods.dev/badge/commands/opensesh/karimo-overview/greptile-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/opensesh/karimo-overview/greptile-review"><img src="https://agentmods.dev/badge/commands/opensesh/karimo-overview/greptile-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.00000 | $0.04795 |
| Opus 5.5 | $0.00000 | $0.01918 |
| Sonnet 5.5 | $0.00000 | $0.00959 |
| Haiku 4.5 | $0.00000 | $0.00479 |
Grade A, and why
greptile-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 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.
This is a copy
100% identical to greptile-review — 43 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.
How it starts
The opening of the file, as written. The whole thing — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/karimo:greptile-review — Standalone Greptile Review Loop
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.
Arguments
--pr <number>(required): The PR number to review.--threshold <1-5>(optional): Target score (default: from config.yaml or 5).--max-loops <1-30>(optional): Maximum revision attempts (default: from config.yaml or 3).--early-exit <1-5>(optional): Score at which to prompt for early exit (default: threshold - 1).--auto(optional): Skip early exit prompts. Continue to threshold or max loops.--no-prompt(optional): Alias for --auto. For CI/CD environments.
Usage
# Standard usage (reads config from config.yaml)
/karimo:greptile-review --pr 123
# Override threshold and max loops
/karimo:greptile-review --pr 123 --threshold 4 --max-loops 2
# Extended loop with budget-aware early exit
/karimo:greptile-review --pr 123 --max-loops 10
# Skip early exit prompts (CI/CD mode)
/karimo:greptile-review --pr 123 --max-loops 10 --auto
# Called by /karimo:merge (internal use)
/karimo:greptile-review --pr 123 --internal
Prerequisites
- Greptile configured —
review.provider: greptilein.karimo/config.yaml - Greptile GitHub App installed — On the repository
- Repository indexed — In Greptile dashboard (app.greptile.com)
- PR exists and is open — Cannot review closed or merged PRs
Behavior
Step 1: Initialize
# Load configuration
review_provider=$(yq '.review.provider' .karimo/config.yaml)
threshold=${THRESHOLD:-$(yq '.review.threshold // 5' .karimo/config.yaml)}
max_loops=${MAX_LOOPS:-$(yq '.review.max_revision_loops // 3' .karimo/config.yaml)}
# Validate Greptile is configured
if [ "$review_provider" != "greptile" ]; then
echo "❌ Greptile not configured"
echo " Run: /karimo:configure --greptile"
exit 1
fi
# Validate PR exists and is open
pr_state=$(gh pr view $pr_number --json state --jq '.state')
if [ "$pr_state" != "OPEN" ]; then
echo "❌ PR #$pr_number is not open (state: $pr_state)"
exit 1
fi
# Get PR metadata for context
pr_branch=$(gh pr view $pr_number --json headRefName --jq '.headRefName')
pr_base=$(gh pr view $pr_number --json baseRefName --jq '.baseRefName')
pr_title=$(gh pr view $pr_number --json title --jq '.title')
echo "╭────────────────────────────────────────────────╮"
echo "│ Greptile Review: PR #$pr_number"
echo "╰────────────────────────────────────────────────╯"
echo ""
echo " Branch: $pr_branch → $pr_base"
echo " Title: $pr_title"
echo " Threshold: ${threshold}/5"
echo " Max loops: $max_loops"
echo ""
echo " Budget reminder: Greptile is \$30/month for 50 PRs, then \$1/PR after."
echo ""
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 · 550 lines · 0 tokens per session scan A ee86edc3c7f2
greptile-review is a command published in the GitHub repository opensesh/karimo-overview (11 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,795 tokens. A static security scan graded it A with 0 findings. It is 100% identical to greptile-review, differing in 43 lines, and is treated as a copy.
Other commands, from other repositories
dashboard
Phase 3 monitoring — System health, execution insights, and velocity analytics.
doctor
Check the health of a KARIMO installation, identify issues, and provide actionable recommendations.
run
Execute an approved PRD using feature branch workflow (v7.0). This command generates briefs, auto-reviews them, allows user iteration, and then orchestrates execution.
merge
Consolidate feature branch changes and create final PR to main. This completes the v5.0 feature branch workflow after all task PRs have been merged.
greptile-review
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.
feedback
Intelligent feedback capture with automatic complexity detection and adaptive investigation.