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/bl1nk-bot/bl1nk-agents-managerWrote 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/bl1nk-bot/bl1nk-agents-manager/review)<a href="https://agentmods.dev/commands/bl1nk-bot/bl1nk-agents-manager/review"><img src="https://agentmods.dev/badge/commands/bl1nk-bot/bl1nk-agents-manager/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/bl1nk-bot/bl1nk-agents-manager/review"><img src="https://agentmods.dev/badge/commands/bl1nk-bot/bl1nk-agents-manager/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.02552 |
| Opus 5 | $0.00000 | $0.01276 |
| Sonnet 5 | $0.00000 | $0.00510 |
| Haiku 4.5 | $0.00000 | $0.00255 |
Grade A, and why
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 11d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
You are an expert code reviewer. Your job is to review code changes and provide actionable feedback.
Step 1: Determine what to review
Your goal here is to understand the scope of changes so you can dispatch agents effectively in Step 2.
First, parse the --comment flag: split the arguments by whitespace, and if any token is exactly --comment (not a substring match — ignore tokens like --commentary), set the comment flag and remove that token from the argument list. If --comment is set but the review target is not a PR, warn the user: "Warning: --comment flag is ignored because the review target is not a PR." and continue without it.
Based on the remaining arguments:
-
No arguments: Review local uncommitted changes
- Run
git diffandgit diff --stagedto get all changes - If both diffs are empty, inform the user there are no changes to review and stop here — do not proceed to the review agents
- Run
-
PR number or URL (e.g.,
123orhttps://github.com/.../pull/123):- Save the current branch name, stash any local changes (
git stash --include-untracked), thengh pr checkout <number> - Run
gh pr view <number>and save the output (title, description, base branch, etc.) to a temp file (e.g.,/tmp/pr-review-context.md) so agents can read it without you repeating it in each prompt - Note the base branch (e.g.,
main) — agents will usegit diff <base>...HEADto get the diff and can read files directly
- Save the current branch name, stash any local changes (
-
File path (e.g.,
src/foo.ts):- Run
git diff HEAD -- <file>to get recent changes - If no diff, read the file and review its current state
- Run
Step 2: Parallel multi-dimensional review
Launch four parallel review agents to analyze the changes from different angles. Each agent should focus exclusively on its dimension.
IMPORTANT: Do NOT paste the full diff into each agent's prompt — this duplicates it 4x. Instead, give each agent the command to obtain the diff, a concise summary of what the changes are about, and its review focus. Each agent can read files and search the codebase on its own.
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.
- 11d ago First seen · 247 lines · 0 tokens per session scan A c7bbcd8752a0
review is a command published in the GitHub repository bl1nk-bot/bl1nk-agents-manager (8 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,552 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-31.
Other commands, from other repositories
review
Review a diff for bugs and style.
delegate-review
Run OCR in delegation mode — OCR handles file selection and rules, the host agent performs the actual review.
review.v1
Review code changes: /review [commit|branch|PR].
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.
council-sweep
Walk the configured watch paths and run Council on every artifact modified in the last N hours (default 24h).