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 skills add mostafa-drz/claude-skills --skill post-pr-for-reviewgit clone --depth 1 https://github.com/mostafa-drz/claude-skillsWrote 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/mostafa-drz/claude-skills/post-pr-for-review)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/post-pr-for-review"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/post-pr-for-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/mostafa-drz/claude-skills/post-pr-for-review"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/post-pr-for-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.00068 | $0.02287 |
| Opus 5 | $0.00034 | $0.01144 |
| Sonnet 5 | $0.00014 | $0.00457 |
| Haiku 4.5 | $0.00007 | $0.00229 |
Grade A, and why
post-pr-for-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 today.
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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post PR for Review
Generate a contextual Slack message for posting a PR to the team's review channel.
Preferences
Read ~/.claude/skills/post-pr-for-review/preferences.md using the Read tool. If not found, no preferences are set — using defaults.
Context
On startup, use Bash to detect: current git branch, repo name, org (gh repo view --json owner -q .owner.login), and your open PRs (gh pr list --author @me --state open --limit 5). Skip any that fail.
Command Routing
Check $ARGUMENTS:
help→ display help then stopconfig→ interactive setup then stopreset→ delete preferences, confirm, stop- anything else → generate the Slack message
Help
If $ARGUMENTS is "help" (case-insensitive), display:
Post PR for Review
Generate a Slack message for posting a PR to the team's review channel.
Usage:
/post-pr-for-review 393 PR in current repo
/post-pr-for-review 393 ai-assemble PR in specific repo
/post-pr-for-review <github-url> PR from full URL
/post-pr-for-review config Configure defaults
/post-pr-for-review reset Clear preferences
/post-pr-for-review help Show this help
Context sources:
PR Title, description, diff, files changed
Linear Linked ticket objective, project, status
Session Current conversation, decisions made, files discussed
Related Other open PRs in the same project/initiative
Configurable:
Detail level Minimal (1 line) | Standard (1-3 lines) | Detailed (with context)
Tone Neutral | Conversational
Extras Reviewer tags, related PRs, testing notes, side effects
Then stop.
Config
If $ARGUMENTS is "config" or "configure" (case-insensitive), use AskUserQuestion:
Q1 — "Default detail level?" (multiSelect: false)
- Standard (1-3 sentences) (Recommended)
- Minimal (1 sentence)
- Detailed (with testing notes, side effects, related PRs)
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.
- today Changed · +3 lines 439d37abf4ef
- 12d ago First seen · 284 lines · 68 tokens per session scan A 21d1d1cb809d
post-pr-for-review is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 2,287 once invoked, about $0.0003 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
review-implementing
Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.
code-auditor
Performs comprehensive codebase analysis covering architecture, code quality, security, performance, testing, and maintainability. Use when user wants to audit code quality, identify technical debt, find security issues, assess test coverage, or get a codebase health check.
agentic-review
Deep multi-agent code review for local changes. Inspired by AmpCode's agentic review. Use when you want comprehensive analysis of staged changes, unstaged changes, specific commits, or branch differences. Spawns parallel specialized agents (security, performance, patterns, architecture) and synthesizes actionable…
qa
Full QA on all session changes using Codex as a second pair of eyes. Use when user says "QA", "full QA", "QA my changes", "QA all your changes", or "use codex to review". Runs git diff, sends changes to Codex for thorough review, and synthesizes findings.
shipkit-review-shipping
Review changes across 12 quality dimensions and report findings. Use after a chunk of work or before commit.
shipkit-prompt-audit
Audit LLM prompt pipeline architecture — decomposition, parallelization, chain integrity, schema validation, fallback paths. Finds structural issues no linter catches.