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/create-prnpx skills add ReflexioAI/reflexio --skill create-prgit 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.00074 | $0.01341 |
| Opus 5 | $0.00037 | $0.00671 |
| Sonnet 5 | $0.00015 | $0.00268 |
| Haiku 4.5 | $0.00007 | $0.00134 |
Grade A, and why
create-pr scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
<How the changes were verified — manual testing steps, automated tests run, curl commands, etc.> This is a copy
100% identical to create-pr — 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Creator
Create well-structured, reviewer-friendly pull requests following best practices.
CRITICAL: This skill MUST always result in a PR being created. Do NOT stop early, do NOT ask the user to run another command first. Handle all prerequisites (committing, branching, pushing) inline and proceed to gh pr create.
Workflow
Step 1: Pre-flight Checks
Run these checks before anything else:
- Verify GitHub CLI authentication — run
gh api user --jq '.login'to confirm the CLI is authenticated. If this fails, tell the user to rungh auth loginfirst and stop. - Determine the base branch — default to
main. If the user specifies a different base, use that. Capture as$BASE_BRANCH.
Step 2: Commit Uncommitted Changes
Run git status to check for uncommitted changes. If there are uncommitted changes, commit them directly — do NOT delegate to another skill or tell the user to commit first.
- Stage changes — run
git add <files>for relevant modified/untracked files. Do not stage.envor gitignored files. - Lint and format — if Python files are staged, run:
Re-stage any modified files.ruff check --fix <files> && ruff format <files> - Commit — write a conventional commit message based on the staged diff:
If precommit hooks modify files, re-stage withgit commit -m "<type>: <description>"git add -uand retry (up to 3 times).
Step 3: Ensure Feature Branch
- Check current branch — run
git branch --show-current. - If on
$BASE_BRANCH, create a feature branch:- Analyze the commits/changes to pick a descriptive name (e.g.,
feat/add-auth,fix/login-bug) - Run
git checkout -b <branch-name>
- Analyze the commits/changes to pick a descriptive name (e.g.,
- If on a different branch, check whether the branch has PR-worthy commits vs
$BASE_BRANCH:- Run
git log $BASE_BRANCH..HEAD --oneline - If there are commits, use the current branch as-is
- If there are NO commits (branch is at same point as base), this means something went wrong — investigate and fix
- Run
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 · 140 lines · 74 tokens per session scan A afdd81ca687c
create-pr is a skill published in the GitHub repository ReflexioAI/reflexio (338 stars, last pushed 2d ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,341 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to create-pr, 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.