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.
npx skills add benchflow-ai/benchflow --skill followup-benchgit clone --depth 1 https://github.com/benchflow-ai/benchflowWrote 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/skills/benchflow-ai/benchflow/followup-bench)<a href="https://agentmods.dev/skills/benchflow-ai/benchflow/followup-bench"><img src="https://agentmods.dev/badge/skills/benchflow-ai/benchflow/followup-bench/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/skills/benchflow-ai/benchflow/followup-bench"><img src="https://agentmods.dev/badge/skills/benchflow-ai/benchflow/followup-bench.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00183 |
| Opus 5.5 | $0.00012 | $0.00073 |
| Sonnet 5.5 | $0.00006 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
independent-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.
What it actually says
Independent Review Skill
When an independent reviewer provides feedback on your code, incorporate it effectively.
Process
- Read the reviewer's feedback carefully
- Identify each specific issue raised
- Fix only what the reviewer flagged — don't refactor unrelated code
- If the reviewer says the code is correct, don't make unnecessary changes
- Verify your fixes address each point
When reviewer finds bugs
- Fix each bug the reviewer identified
- Add edge case handling if reviewer pointed out missing cases
- Test mentally that the fix resolves the specific issue
When reviewer approves
- Acknowledge the positive review
- Do NOT introduce unnecessary changes to working code
- "If it ain't broke, don't fix it"
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 29 lines · 29 tokens per session scan A 71538c88739b
independent-review is a skill published in the GitHub repository benchflow-ai/benchflow (355 stars, last pushed 7d ago), licensed Apache-2.0. It adds 29 tokens to every session and 183 once invoked, about $0.0001 per session on Opus 5.5. 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 skills, from other repositories
find-bugs
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.
architect-init
Use when bootstrapping architecture documentation for a brownfield project by reverse-engineering ADRs from an existing codebase.
architect-analyze
Use when validating generated or refined architecture artifacts, before feature development, during architecture review, or periodically to detect ADR↔AD drift, completeness gaps, and quality issues.
factory-review
Use when reviewing PRs for severity-ranked policy compliance against REVIEW.md, babysitting agent PRs to merge, or self-healing Important findings before a human sees them.
code-review
Paranoid architect review of code changes for bugs, security, missing tests, and undocumented assumptions. Works on local git diffs OR a GitHub pull request (e.g. owner/repo N). For PRs, can post findings as line-level review comments.
parallel-pr-review
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.