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.
git clone --depth 1 https://github.com/RashadAnsari/myagentsWrote 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/commands/rashadansari/myagents/pr-review)<a href="https://agentmods.dev/commands/rashadansari/myagents/pr-review"><img src="https://agentmods.dev/badge/commands/rashadansari/myagents/pr-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/commands/rashadansari/myagents/pr-review"><img src="https://agentmods.dev/badge/commands/rashadansari/myagents/pr-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.00047 | $0.05060 |
| Opus 5 | $0.00023 | $0.02530 |
| Sonnet 5 | $0.00009 | $0.01012 |
| Haiku 4.5 | $0.00005 | $0.00506 |
Grade C, and why
pr-review scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
If any command fails, clean up with `rm -rf "$REVIEW_DIR"` and report the error. How it starts
The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MANDATORY: Load the humanizer skill (albino:humanizer) now and keep all its rules active for the entire session. Every piece of text you write or post, including comment bodies, the review body, and any output to the user, must pass the humanizer check before it leaves your context.
PR Review
Review the GitHub pull request: $ARGUMENTS
Step 1: Validate Input
If $ARGUMENTS is empty or missing, stop immediately and tell the user:
Usage: /pr-review <github-pr-url>
Example: /pr-review https://github.com/owner/repo/pull/123
Parse owner, repo, and number from $ARGUMENTS now (URL format: https://github.com/{owner}/{repo}/pull/{number}). If the URL does not match this format, stop and show the usage message above.
Step 2: Pre-Review Gate
Run both in parallel:
gh pr view "$ARGUMENTS" --json state,isDraft,author --jq '{state: .state, isDraft: .isDraft, author: .author.login}'
gh api repos/{owner}/{repo}/pulls/{number}/reviews --jq '[.[].user.login]'
Stop immediately with a clear message if any condition is true:
stateis not"OPEN"(PR is closed or merged)isDraftistrueauthor.loginends in[bot]or is one of:dependabot,renovate,snyk-bot,github-actions- The authenticated user's login already appears in the reviews list (run
gh api user --jq '.login'to get it if needed)
Step 3: Fetch PR Data
Run all three in parallel:
gh pr view "$ARGUMENTS" --json number,title,body,author,baseRefName,headRefName,headRefOid,state,additions,deletions,changedFiles
gh pr view "$ARGUMENTS" --json files --jq '[.files[].path]'
gh pr diff "$ARGUMENTS"
If any command fails, stop and report the error. If not authenticated, suggest gh auth login.
Store:
PR_META: parsed JSON from the first commandCHANGED_FILES: list of changed file paths from the second commandPR_DIFF: full diff text from the third commandHEAD_SHA: value ofheadRefOidfromPR_META
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 Changed · +2 lines acddf3ce6bff
- 9d ago First seen · 333 lines · 47 tokens per session scan C 4f185a92c7da
pr-review is a command published in the GitHub repository RashadAnsari/myagents (6 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 5,060 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
revert
Git-aware undo by logical work unit (track, phase, or task).
team-review
Launch a multi-reviewer parallel code review with specialized review dimensions.
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
pr-reviewer
Review a Git branch as a PR against the base branch (auto-resolved — main/master) judged by THIS repo's contract (CLAUDE.md + .claude/skills/). Three-dot diff, route changed paths to skills, verify (eslint/prettier/tsc + tests), tiered report + confidence. Optional gated fix + commit after the report.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.