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 harness/harness-skills --skill pr-analysisgit clone --depth 1 https://github.com/harness/harness-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/harness/harness-skills/pr-analysis)<a href="https://agentmods.dev/skills/harness/harness-skills/pr-analysis"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/pr-analysis.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00111 | $0.01337 |
| Opus 5 | $0.00056 | $0.00668 |
| Sonnet 5 | $0.00022 | $0.00267 |
| Haiku 4.5 | $0.00011 | $0.00134 |
Grade A, and why
pr-analysis 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pr-analysis — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Analysis
Analyze pull request pipeline impact, run security-focused reviews, and track PRs from merge to production deployment.
Instructions
Step 1: Establish Scope
Confirm the service, repository, and PR details.
Call MCP tool: harness_list
Parameters:
resource_type: "pipeline"
org_id: "<organization>"
project_id: "<project>"
Step 2: Identify the PR Analysis Task
Determine which analysis the user needs:
- PR Pipeline Impact Analysis -- Which pipelines, services, and environments are affected
- Security-Focused PR Review -- Check for secrets, vulnerabilities, and compliance issues
- PR to Production Tracker -- Track a PR from merge through deployment and verification
Step 3: PR Pipeline Impact Analysis
Gather from the user:
- Service name and repository
- PR description and changed components (files/directories modified)
Identify affected resources:
Call MCP tool: harness_list
Parameters:
resource_type: "trigger"
org_id: "<organization>"
project_id: "<project>"
Analyze impact:
- Pipelines triggered: Which CI/CD pipelines will fire on merge (based on triggers and path filters)
- Services affected: Which Harness services reference the changed code or manifests
- Environments reached: Which environments will receive the change (dev, staging, prod)
- Downstream impact: Other services that depend on the changed service
- Infrastructure changes: Any Terraform, Helm, or Kubernetes manifest changes
Present findings as:
- DIRECT IMPACT: Pipelines and services directly triggered
- INDIRECT IMPACT: Downstream services and dependent deployments
- RISK LEVEL: Low (test/docs only), Medium (application code), High (infrastructure/security/config)
Step 4: Security-Focused PR Review
Gather from the user:
- Service name and repository
- PR description and changed components
Security checklist:
Secrets and Credentials:
- Scan for hardcoded secrets, API keys, tokens, or passwords in the diff
- Check for new environment variables that should use Harness Secrets
- Verify no secrets are logged or exposed in error messages
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.
- 8d ago First seen · 173 lines · 111 tokens per session scan A 0e2531ed7793
pr-analysis is a skill published in the GitHub repository harness/harness-skills (104 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 111 tokens to every session and 1,337 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
migration-review
Review database migration files when a change adds or modifies paths under migrations/. Use it before merge to collect forward, rollback, locking, and data-safety evidence.
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.
github-review-pr
Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for…
review-export
Export CocoReview reports as markdown, html, or pdf-ready status artifacts. Usage: $review export markdown|html|pdf [report-path].
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
fkteams
A command-line tool and web interface for asking AI models questions, reviewing code, and running multi-agent discussions. A command-line tool is software controlled by typing commands in a terminal.