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/dinnovos/dinnovos-marketplaceWrote 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/dinnovos/dinnovos-marketplace/bro-review-this)<a href="https://agentmods.dev/commands/dinnovos/dinnovos-marketplace/bro-review-this"><img src="https://agentmods.dev/badge/commands/dinnovos/dinnovos-marketplace/bro-review-this/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/dinnovos/dinnovos-marketplace/bro-review-this"><img src="https://agentmods.dev/badge/commands/dinnovos/dinnovos-marketplace/bro-review-this.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.00020 | $0.03508 |
| Opus 5 | $0.00010 | $0.01754 |
| Sonnet 5 | $0.00004 | $0.00702 |
| Haiku 4.5 | $0.00002 | $0.00351 |
Grade A, and why
bro-review-this scanned grade A with 1 finding 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 12d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
| Python | `os.system(f"ping {h}")` | `subprocess.run(['ping', h])` | How it starts
The opening of the file, as written. The whole thing — 481 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Analyze the specified code and generate a detailed report. Read-only, doesn't modify anything. Multi-language support.
User Input
The user can specify what to review in various ways:
Exact path:
/bro-review-this src/components/Button.tsx/bro-review-this src/hooks//bro-review-this internal/handlers/
Natural language (illustrative examples):
/bro-review-this review the <name> component/bro-review-this review the <feature> services/bro-review-this analyze the <feature> module/bro-review-this review everything related to <topic>
No arguments:
/bro-review-this→ analyzes the entire project
Note: Terms like "login", "users", "payments" are just examples. Interpret what the user requests and search for the corresponding files in the project.
Step 1: Interpret the Request
If it's an exact path:
Use directly.
If it's natural language:
Search for files matching the description:
# Explore project structure (all extensions)
find . -type f \( -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.jsx" -o -name "*.py" -o -name "*.go" -o -name "*.rs" -o -name "*.php" -o -name "*.rb" -o -name "*.java" -o -name "*.cs" -o -name "*.kt" \) | grep -v node_modules | grep -v vendor | grep -v target | grep -v __pycache__ | grep -v dist | grep -v .git
# Search by related name (replace <term> with what the user requested)
find . -type f -iname "*<term>*" | grep -v node_modules
find . -type d -iname "*<term>*" | grep -v node_modules
# Search related content
grep -ril "<term>" --include="*.ts" --include="*.tsx" --include="*.js" --include="*.py" --include="*.go" --include="*.rs" --include="*.php" | grep -v node_modules | head -20
Confirm with the user if you find multiple matches:
Found these files related to "<term>":
1. src/components/[File1].tsx
2. src/hooks/[File2].ts
3. src/services/[File3].ts
Should I review all of them or a specific one?
If there's only one clear match, proceed directly.
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.
- 12d ago First seen · 481 lines · 20 tokens per session scan A 881030cc4192
bro-review-this is a command published in the GitHub repository dinnovos/dinnovos-marketplace (2 stars, last pushed 7mo ago), licensed MIT. It adds 20 tokens to every session and 3,508 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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 }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.