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 agentmods add skills/benchflow-ai/benchflow/task-reviewnpx skills add benchflow-ai/benchflow --skill task-reviewgit clone --depth 1 https://github.com/benchflow-ai/benchflowWhat 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 | $0.00141 | $0.04585 |
| Opus 5 | $0.00071 | $0.02292 |
| Sonnet 5 | $0.00028 | $0.00917 |
| Haiku 4.5 | $0.00014 | $0.00458 |
Grade B, and why
task-review scanned grade B with 2 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. The user's own configs: `cat ~/.codex/config.toml` (often pins a Codex model + reasoning effort), `~/.claude/settings.json` for Claude. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `verifier/test_outputs.py` imports a network client (`exa_py`, `requests`, `urllib`, `httpx`, `googleapiclient`) used during verification | **research-track** | This is a copy
95% identical to task-review — 7 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SkillsBench Task Review
Repo context. This skill lives in the
benchflowrepo but reviews PRs againstbenchflow-ai/skillsbench. Unqualified references below —CONTRIBUTING.md,MAINTAINER.md,docs/*.md,tasks/<task-id>/— mean files in skillsbench.scripts/fetch_pr.shdefaults to that repo; override withSKILLSBENCH_REPO. For auditing already-published run trajectories, usebenchflow-experiment-reviewinstead.
End-to-end review of a SkillsBench task PR. Two artifacts are produced: a human-readable .txt report, and a pr<N>.zip bundle that mirrors the format reviewers post on PRs (see PR #560 comment for the reference structure).
Workflow
1. fetch → pull PR files into a workspace (no git checkout)
2. route → classify task track; pick the track-specific rubric
3. policy → static checks against rubric (no execution)
4. benchmark → 5 configs: oracle + claude×{skills,no} + codex×{skills,no}
5. audit → read trajectories: skill use, cheating, root cause of failures
6. report → fill report-template.txt and bundle pr<N>.zip
Each step is described below. Run them in order — never skip benchmark to write a verdict, never skip audit to interpret results.
Step 1 — Fetch the PR
scripts/fetch_pr.sh <pr_number> <workspace>
# → echoes the task dir path; writes <workspace>/pr-<N>.meta.json with PR metadata.
Use gh API + raw download. Do not gh pr checkout or git pull — keep the local clone clean. For a local-path review, skip this step and pass the task directory directly to step 3.
Step 2 — Route to a track
A SkillsBench task belongs to one of three tracks. The track determines what "verifiable" means and which policy items apply. Always classify before running policy checks — applying the wrong rubric is the most common reason a review goes sideways.
What ships with it
12 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.
- assets/audit-example.json 4.0 KB
- assets/report-template.txt 5.8 KB
- goodtask-v2.md 27 KB
- references/audit-general.md 19 KB
- references/audit-skillsbench.md 8.7 KB
- references/policy-rubric.md 6.2 KB
- references/track-routing.md 7.4 KB
- references/trajectory-audit.md 2.0 KB
- scripts/fetch_pr.sh 1.9 KB runs code
- scripts/package_traj.sh 1.5 KB runs code
- scripts/parse_results.py 2.9 KB runs code
- scripts/run_experiments.sh 4.2 KB runs code
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.
- 2d ago First seen · 213 lines · 141 tokens per session scan B e31fc162d21e
task-review is a skill published in the GitHub repository benchflow-ai/benchflow (335 stars, last pushed 3d ago), licensed Apache-2.0. It adds 141 tokens to every session and 4,585 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). It is 95% identical to task-review, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
lastlight-evals
Scaffold, configure and run a Last Light EVALS workspace — the harness that runs Last Light's real workflows against a mocked GitHub and grades them deterministically. Use when the user wants to "set up / scaffold Last Light Evals", "create an evals workspace or instance", "run evals", "compare models", or author new…
mobile-principles
Mobile-specific UX principles - touch targets, hover-less doctrine, thumb zones, safe areas, gestures, mobile perf budgets. Cross-platform (web mobile, iOS, Android).
canvas-generative
Algorithmic and generative art with Canvas 2D - particles, flow fields, noise, fractals, L-systems.
threejs-r3f
Three.js and React Three Fiber sub-skill - 3D scenes, shaders, postprocessing.
portfolio
Cross-chain DeFi portfolio discovery, rebalancing suggestions, and NEAR Intent construction. Activates when the user pastes a wallet address or asks about yield/positions/rebalancing. Bootstraps a per-user "portfolio" project, aggregates positions across all the user's addresses inside one project, and offers a…
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.