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 manage-pull-requestsgit 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/manage-pull-requests)<a href="https://agentmods.dev/skills/harness/harness-skills/manage-pull-requests"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/manage-pull-requests/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/harness/harness-skills/manage-pull-requests"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/manage-pull-requests.svg" alt="Reviewed on agentmods" width="80" 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.00123 | $0.02572 |
| Opus 5 | $0.00062 | $0.01286 |
| Sonnet 5 | $0.00025 | $0.00514 |
| Haiku 4.5 | $0.00012 | $0.00257 |
Grade A, and why
manage-pull-requests 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 10d 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:
- manage-pull-requests — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Pull Requests
Manage Harness Code pull requests, reviewers, comments, checks, and activity via MCP.
MCP Tools Used
| Tool | Resource Type | Purpose |
|---|---|---|
harness_list |
pull_request |
List PRs in a repo, filter by state |
harness_get |
pull_request |
Get PR details by number |
harness_create |
pull_request |
Open a new PR |
harness_update |
pull_request |
Update PR title / description / state |
harness_execute (action: merge) |
pull_request |
Merge a PR (merge/squash/rebase/fast-forward) |
harness_list |
pr_reviewer |
List reviewers on a PR |
harness_create |
pr_reviewer |
Add a reviewer to a PR |
harness_execute (action: submit_review) |
pr_reviewer |
Submit an approved or changereq review |
harness_create |
pr_comment |
Post a top-level or inline code comment |
harness_update |
pr_comment |
Edit a comment |
harness_delete |
pr_comment |
Delete a comment |
harness_list |
pr_activity |
Read the discussion timeline — the only way to READ comments |
harness_list |
pr_check |
List CI status checks on a PR |
harness_schema |
any of the above | Exact JSON Schema for create / update body fields |
All pull-request resources are repo-scoped. Every call needs repo_id and pr_number (except harness_list for pull_request, which only needs repo_id). org_id / project_id are optional (the server infers them from the repo).
URL shortcut: the MCP server auto-extracts repo_id and pr_number if you pass a Harness PR URL via the url parameter — e.g. harness_get(resource_type="pull_request", url="https://app.harness.io/ng/account/.../pulls/42").
Instructions
Step 1: List or find the PR
Call MCP tool: harness_list
Parameters:
resource_type: "pull_request"
repo_id: "<repository_identifier>"
state: "open" # optional: open | closed | merged
query: "<keyword>" # optional: full-text search
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.
- 10d ago First seen · 304 lines · 123 tokens per session scan A 2255093ae6b9
manage-pull-requests is a skill published in the GitHub repository harness/harness-skills (105 stars, last pushed yesterday), licensed Apache-2.0. It adds 123 tokens to every session and 2,572 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
hunk-extensions
Maps the hunkdiff/extension authoring surface for Hunk, the terminal diff viewer — hiding or reordering reviewed files, docked panes, alternate file views, commands and key bindings, dialogs, workspace writes, themes, syntax languages, VCS backends, lifecycle events. Use when writing, debugging, or installing a Hunk…
hunk-launch-video
Produces Hunk videos by driving the real TUI headlessly in a PTY, compositing captioned 1080p frames in Chromium, and encoding with ffmpeg. Use for feature demos, workflow explainers, announcements, launch videos, and full-release roundups.
hunk-release
Prepares, publishes, verifies, and curates Hunk releases. Use for release metadata, benchmarks, tags, publishing, release videos, backports, or recovery.
hunk-review
Interacts with live Hunk diff review sessions via CLI. Inspects review focus, navigates files, hunks, and exact lines, reloads session contents, adds inline review comments, and paints attention marks on character ranges. Use when the user has a Hunk session running or wants to review diffs interactively.
pr-review
Review open PRs two ways - default is a per-PR deep review with severity-tagged findings, inline comments, and a verdict; --survey runs a risk-tiered triage digest of what's safe to merge first.
pr-triage
First-touch triage for external pull requests - verdict, label, and a welcoming comment within minutes of open.