Borrowing it
Nothing to install: this file belongs to geserdugarov/agent-orchestrator. 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/geserdugarov/agent-orchestrator/main/.agents/skills/review/SKILL.mdgit clone --depth 1 https://github.com/geserdugarov/agent-orchestratorWrote 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/geserdugarov/agent-orchestrator/review)<a href="https://agentmods.dev/skills/geserdugarov/agent-orchestrator/review"><img src="https://agentmods.dev/badge/skills/geserdugarov/agent-orchestrator/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/skills/geserdugarov/agent-orchestrator/review"><img src="https://agentmods.dev/badge/skills/geserdugarov/agent-orchestrator/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.00029 | $0.01688 |
| Opus 5 | $0.00015 | $0.00844 |
| Sonnet 5 | $0.00006 | $0.00338 |
| Haiku 4.5 | $0.00003 | $0.00169 |
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 10d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewer skill — agent-orchestrator
CI / lint
Reject (or request fixes) if any of these are red:
ruff check orchestrator tests. Common offenders to look for explicitly:- F401 — unused import on a package initializer. If the import is intended as a re-export, it must
be aliased
from X import Y as Yor listed in that initializer's__all__. A bare import will not survive ruff. - F541 — f-strings without placeholders, typically in newly-added test files.
- F841 — unused local in tests.
- E402 — import after non-import code.
- F401 — unused import on a package initializer. If the import is intended as a re-export, it must
be aliased
uv run flake8 orchestrator tests --select=WPS. All WPS naming, complexity, consistency, bug-prevention, refactoring, and OOP findings are rejection criteria.git diff --check origin/main...HEAD— trailing whitespace and blank lines at EOF. Check it even if everything else looks clean.- Full
pytestrun is referenced in the PR description and passes end-to-end. Reject "known failure" hand-waves; if the PR claims a baseline failure, the description must include a reproduction onorigin/mainat the branch point. Otherwise the developer must fix it. - Every source file the PR adds (
*.py,*.sh,pyproject.toml) opens with the# Copyright 2026 Geser Dugarov/# SPDX-License-Identifier: Apache-2.0header pair.
Behavior preservation
For any refactor:
- Workflow labels, pinned-state JSON keys, comment marker text, watermark fields, and event-emission
shape must match
mainexactly. Issues already in flight depend on these — a rename is a migration, not a refactor. - Spot-check that moved code still routes through the same auth / fetch / push / retry helpers. A refactor is not allowed to silently change side effects.
- Squash-on-approval, the in_review HITL ready-ping gates (mergeable + approved + no standing CHANGES_REQUESTED), retry budgets, and stale-session detection are easy to break by accident during a move; verify their call paths survive intact.
Module boundaries
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.
- 10d ago First seen · 126 lines · 29 tokens per session scan A 1b215880e24a
review is a skill published in the GitHub repository geserdugarov/agent-orchestrator (10 stars, last pushed 10d ago), licensed Apache-2.0. It adds 29 tokens to every session and 1,688 once invoked, about $0.0001 per session on Opus 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-31.
Other skills, from other repositories
do-it-review
Use to assess requirements and implementation quality independently, or to resolve a batch of review findings.
github-code-review
Comprehensive GitHub code review with AI-powered swarm coordination.
noslop-pr-gate
Run the noslop pre-PR quality gate and handle the noslop-approved escape hatch for intentional config weakening before opening a pull request.
resolve-comments
Use when resolving unresolved PR or MR review comments, working through reviewer feedback, or addressing code review threads on GitHub, GitLab, Bitbucket Cloud, or Azure DevOps repositories.
github-code-review
Comprehensive GitHub code review with AI-powered swarm coordination.
gh-review-followthrough
Address GitHub PR review threads or issue comments with explicit comment selection, repo-grounded fixes, and concise reply-ready summaries.