Borrowing it
Nothing to install: this file belongs to Insight-Services-APAC/ingenious. 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/Insight-Services-APAC/ingenious/main/.claude/commands/analysis/honest-review.mdgit clone --depth 1 https://github.com/Insight-Services-APAC/ingeniousWrote 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/insight-services-apac/ingenious/honest-review)<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/honest-review"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/honest-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/insight-services-apac/ingenious/honest-review"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/honest-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.00415 |
| Opus 5 | $0.00000 | $0.00208 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
honest-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 4d 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
Honest Code Review
Perform a brutally honest code review. Do not soften feedback or use diplomatic language. State problems directly.
Review Scope
Review the code changes or files specified. If none specified, review recent uncommitted changes.
Review Criteria
Correctness
- Does this code actually work? Are there edge cases that will break it?
- Are there logic errors or off-by-one mistakes?
- Will this fail silently or produce wrong results?
Design Problems
- Is this the wrong approach entirely?
- Is this over-engineered for what it does?
- Is this under-engineered and will cause problems later?
- Does this duplicate existing functionality?
Code Quality
- Is this code hard to read or understand?
- Are the names misleading or unclear?
- Is the structure confusing?
- Would you struggle to debug this at 3am?
Security & Reliability
- Are there obvious security holes?
- Will this break under load or unusual conditions?
- Are errors handled properly or swallowed?
Maintenance Burden
- Will future developers curse this code?
- Is this adding unnecessary complexity?
- Does this violate established patterns in the codebase?
Output Format
Be direct. No praise sandwiches. No "great job but...". Just state the issues.
Critical Issues - Things that must be fixed before merge Problems - Things that should be fixed but won't cause immediate harm Concerns - Things worth discussing or reconsidering Verdict - APPROVE, NEEDS CHANGES, or REJECT with a one-line summary
Example output style:
CRITICAL: The SQL query on line 45 is vulnerable to injection.
PROBLEM: The function `processData` does three unrelated things.
CONCERN: This adds a new dependency for something achievable with stdlib.
VERDICT: NEEDS CHANGES - Fix the SQL injection, consider splitting processData.
Do not add false positives to appear thorough. If the code is genuinely good, say so briefly and move on.
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.
- 4d ago First seen · 56 lines · 0 tokens per session scan A 16f86e170045
honest-review is a command published in the GitHub repository Insight-Services-APAC/ingenious (24 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 415 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-09-04.
Other commands, from other repositories
delegate-review
Run OCR in delegation mode — OCR handles file selection and rules, the host agent performs the actual review.
review
Review code changes against project conventions.
review.v1
Review code changes: /review [commit|branch|PR].
explain
Drive a diff/PR/branch → self-contained interactive HTML explainer via the oma-explanation skill. Resolves the target ref, runs secret gates and the validation checklist, saves under .agents/results/explain/, and reports TL;DR plus path.
branch-review
Review a branch before merge [target] [level].
aidd-churn
Rank files by hotspot score to identify prime candidates for refactoring before PR review.