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/reflexioai/reflexio/reviewnpx skills add ReflexioAI/reflexio --skill reviewgit clone --depth 1 https://github.com/ReflexioAI/reflexioWhat 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.00052 | $0.03186 |
| Opus 5 | $0.00026 | $0.01593 |
| Sonnet 5 | $0.00010 | $0.00637 |
| Haiku 4.5 | $0.00005 | $0.00319 |
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 yesterday.
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.
This is a copy
100% identical to review — 0 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Perform a rigorous, senior-engineer-level code review of all uncommitted changes in the working tree.
Core Principles
- You are a strict reviewer, not a rubber-stamper. Flag real problems. Do not praise code just to be nice.
- Never make changes directly. Your output is a review report and an optional change plan. Wait for explicit user approval before editing any file.
- Embed assumptions inline. If you cannot tell whether something is intentional or a mistake, note your assumption in the report and flag it for confirmation.
- Focus on substance over style. Formatting issues caught by pre-commit hooks are low priority. Lint violations and type errors in changed files are substantive findings — classify them by severity alongside manual review findings.
Review Depth
By default, run the full checklist. If the user requests a quick review (e.g., /review --quick), focus only on:
- Security
- Correctness & Logic
- API & Contract Design
- Error Handling & Resilience
Skip deeper analysis sections (Duplication, Missing Tests, Code Clarity) in quick mode.
Workflow
Phase 1 — Gather the diff
If git diff HEAD produces no output and git status shows no uncommitted changes and no untracked files, inform the user that there are no changes to review and stop.
Run these commands to understand the full scope of uncommitted work:
# Overview of changed files
git status
# Full diff of all tracked changes (staged + unstaged)
git diff HEAD
# List of untracked files that may need review
git ls-files --others --exclude-standard
Read the diff carefully. For every changed file, also read the full file (not just the diff hunk) so you understand the surrounding context — imports, class hierarchy, sibling functions, and call sites.
Run automated checks on changed files (language-aware):
- Detect languages from changed file extensions.
- For Python files (
*.py): runruff check <files>andpyright <files>. - For TypeScript/JavaScript files (
*.ts,*.tsx,*.js,*.jsx,*.mts): runnpx tsc --noEmitandnpx biome check <files>from the relevant project root (reflexio/website/orreflexio/public_docs/). - Skip linters for languages without configured tooling.
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.
- yesterday First seen · 261 lines · 52 tokens per session scan A 09caac7850b4
review is a skill published in the GitHub repository ReflexioAI/reflexio (338 stars, last pushed 2d ago), licensed Apache-2.0. It adds 52 tokens to every session and 3,186 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to review, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
review
Rigorous code review of all uncommitted changes. Analyzes architecture, code quality, security, and engineering best practices. Embeds questions and assumptions inline, then summarizes all proposed changes as a plan for user approval before any edits are made.
fastapi
FastAPI best practices and conventions. Use when working with FastAPI APIs and Pydantic models for them. Keeps FastAPI code clean and up to date with the latest features and patterns, updated with new versions. Write new code or refactor and update old code.
commit
Git commit workflow with precommit hook handling, lint/type checking, README updates, and API reference updates. Use when the user wants to commit changes. Handles precommit hooks that modify files (formatting, linting) by re-staging and retrying. Runs ruff lint and pyright type checks on staged Python files, and…
check-and-test
Run lint checks (ruff for Python, Biome for TS/JS), type checks (pyright for Python, tsc for TS/JS), and the standard pytest tiers (unit + e2e + tests skipped during pre-commit). Investigates failures to determine if they are application bugs or test issues, and fixes application bugs rather than weakening tests. Does…
update-pr
Update an existing pull request with new changes. Use when the user wants to update a PR, push follow-up changes to a PR, refresh a PR description, or sync a PR with latest commits. Triggers on: update pr, update-pr, update the pr, push to pr, refresh pr, sync pr, update pull request.
create-pr
Create high-quality pull requests via gh pr create. Use when the user wants to create a PR, submit a PR, open a pull request, submit for review, or push changes for review. Triggers on: create a pr, create-pr, submit a pr, open a pull request, submit for review, make a pr, gh pr create.