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/appsvortex/arness/arn-reviewing-prnpx skills add AppsVortex/arness --skill arn-reviewing-prgit clone --depth 1 https://github.com/AppsVortex/arnessWrote 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/appsvortex/arness/arn-reviewing-pr)<a href="https://agentmods.dev/skills/appsvortex/arness/arn-reviewing-pr"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-reviewing-pr.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 | $0.00114 | $0.00861 |
| Opus 5 | $0.00057 | $0.00430 |
| Sonnet 5 | $0.00023 | $0.00172 |
| Haiku 4.5 | $0.00011 | $0.00086 |
Grade A, and why
arn-reviewing-pr 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 4d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness Reviewing PR
Validate PR review comments, categorize findings, and fix or defer issues. This is a first-citizen entry point that wraps arn-code-review-pr and provides chaining context back to arn-implementing if fixes are needed.
This skill is a thin orchestration wrapper. It MUST NOT duplicate arn-code-review-pr logic. All review work is done by the invoked skill. Arness-reviewing-pr handles: prerequisite checks, input routing, invoking the review skill, and offering the chain exit.
Step 0: Ensure Configuration
Read ${CLAUDE_PLUGIN_ROOT}/skills/arn-code-ensure-config/references/step-0-fast-path.md and follow its instructions. This guarantees a user profile exists and ## Arness is configured with Arness Code fields before proceeding.
After Step 0 completes, extract the following from ## Arness:
- Platform — determines if PR operations are available (
github,bitbucket, ornone)
If Platform is none: inform the user that no platform is configured and suggest running /arn-reviewing-pr again after configuring a platform. Do not proceed.
Workflow
Step 1: Input Handling
- PR number provided (e.g., "reviewing pr 42", "arness reviewing pr #123"): Extract the PR number and pass it to the review skill.
- No args: Auto-detect PR for current branch (the review skill handles this internally).
- No PR found: The review skill will detect this and inform the user. Suggest running
/arn-shippingto create a PR first.
Step 2: Invoke Review PR
Show progress:
Reviewing PR: REVIEW-PR -> [fix / defer / plan]
^^^^^^^^^
Invoke the review skill:
Skill: arn-code:arn-code-review-pr[optional PR number]
The review skill handles all internal decisions: fetching comments, validating findings, categorizing, and optionally fixing. It has its own user interactions. Wait for it to complete.
Step 3: Completion Handoff
After arn-code-review-pr completes, assess what happened and offer the appropriate chain exit.
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.
- 4d ago First seen · 87 lines · 114 tokens per session scan A d9d3970c5cec
arn-reviewing-pr is a skill published in the GitHub repository AppsVortex/arness (33 stars, last pushed 1mo ago), licensed MIT. It adds 114 tokens to every session and 861 once invoked, about $0.0006 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-30.
Other skills, from other repositories
pulumi-migrate-from-discovered-stack
Migrate a CloudFormation or ARM stack into a Pulumi stack, sourced from a stack that Pulumi Cloud's Discovery feature has already found and exposed via the discovered-stacks API. Load this skill when the user has a discovered stack in Pulumi Cloud and wants to bring its resources under Pulumi management. Do NOT load…
pulumi-component
Guide for authoring Pulumi ComponentResource classes. Use when creating reusable infrastructure components, designing component interfaces, setting up multi-language support, or distributing component packages.
pulumi-overview
Use this skill for any task that creates, modifies, inspects, or destroys cloud infrastructure or SaaS configuration, from one-off CLI operations to full multi-resource projects, across providers in the Pulumi ecosystem. A typical project spans many providers (AWS or Azure or GCP, Kubernetes, Cloudflare, Auth0…
provider-upgrade
Upgrade any Pulumi provider to a newer version and reconcile the resulting diff. Use when users want to upgrade or update a provider (including editing package.json, requirements.txt, pyproject.toml, go.mod, or Pulumi.yaml to bump a provider SDK), check for breaking changes before or during an upgrade, fix resources…
pulumi-best-practices
Load when the user is writing, reviewing, or debugging Pulumi TypeScript/Python programs; asks about Output or apply() usage; wants to create ComponentResource classes; needs to refactor resources without destroying them (aliases); is setting up secrets or config; or is configuring a pulumi preview/up CI workflow.…
pulumi-arm-to-pulumi
Convert or migrate Azure ARM (Azure Resource Manager) templates, Bicep templates, or code to Pulumi, including importing existing Azure resources. This skill MUST be loaded whenever a user requests migration, conversion, or import of ARM templates, Bicep templates, ARM code, Bicep code, or Azure resources to Pulumi.