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/ackeskin/contexture/pr-reviewnpx skills add AcKeskin/contexture --skill pr-reviewgit clone --depth 1 https://github.com/AcKeskin/contextureWrote 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/ackeskin/contexture/pr-review)<a href="https://agentmods.dev/skills/ackeskin/contexture/pr-review"><img src="https://agentmods.dev/badge/skills/ackeskin/contexture/pr-review.svg" alt="Measured on agentmods" 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.00074 | $0.04907 |
| Opus 5 | $0.00037 | $0.02454 |
| Sonnet 5 | $0.00015 | $0.00981 |
| Haiku 4.5 | $0.00007 | $0.00491 |
Grade A, and why
pr-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 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.
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 — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-review
Reviews Pull Requests the user has been assigned to review on GitHub. Fetches PR data via the gh CLI, optionally loads architectural rules via discover, and analyzes the diff across four categories. The terminal report is the live render; the canonical artefact is written to the Obsidian vault (§10) — the user posts their review manually on GitHub; pr-review never posts.
When to run
- User types
/pr-review//pr-review <number>//pr-review <number> <path...>. - Natural language: "review this PR", "review PR 123", "look at pull request 456", "check this pull request".
- Do not auto-fire. User-invoked only. No hook trigger, no session-start trigger, no task-end trigger.
Inputs
- PR number (optional). If omitted, attempt to detect from the current branch via
gh pr view --json number. Bail if no PR is associated. - Path filter (optional). One or more paths to narrow the review scope within the PR diff.
- Working directory —
$CLAUDE_PROJECT_DIRorcwd. Must be inside a git repository with a GitHub remote. ghCLI — required. Bail ifghis not installed or not authenticated.
Procedure
1. Resolve PR target
| Form | Resolution |
|---|---|
/pr-review (no args) |
Run gh pr view --json number,title,state for the current branch. If no PR is associated, bail: "No PR found for the current branch. Pass a PR number: /pr-review <number>." |
/pr-review <number> |
Use the given number directly. |
/pr-review <number> <path...> |
Use the given number; save paths as the path filter for step 5. |
Validate that the PR exists. If the PR is merged or closed, warn:
PR #N is
<state>. Review anyway? (y/N)
Proceed on explicit y.
If the PR is a draft, warn but don't block:
PR #N is a draft. Review anyway? (y/N)
2. Fetch PR metadata
Run:
gh pr view <number> --json number,title,body,state,author,baseRefName,headRefName,url,additions,deletions,changedFiles,labels,commits
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 406 lines · 74 tokens per session scan A 03949c07757d
pr-review is a skill published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 4,907 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
ios-development
Comprehensive guide for building native Apple platform applications.
ai-policy-generator
AI governance policy creation for nonprofits and enterprises with frameworks, risk assessment, ethical guidelines, and compliance templates. Use when drafting AI usage policies, responsible AI frameworks, or organizational AI governance documents.
battle-card-builder
Competitive battle card creation for sales teams combining competitive intelligence, sales enablement, and document formatting. Use when building battle cards, competitive analysis decks, or win/loss analysis materials.