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 harnessprotocol/harness-kit --skill pr-sweepgit clone --depth 1 https://github.com/harnessprotocol/harness-kitWrote 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/harnessprotocol/harness-kit/pr-sweep)<a href="https://agentmods.dev/skills/harnessprotocol/harness-kit/pr-sweep"><img src="https://agentmods.dev/badge/skills/harnessprotocol/harness-kit/pr-sweep/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/harnessprotocol/harness-kit/pr-sweep"><img src="https://agentmods.dev/badge/skills/harnessprotocol/harness-kit/pr-sweep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 130 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00000 | $0.01795 |
| Opus 5.5 | $0.00000 | $0.00718 |
| Sonnet 5.5 | $0.00000 | $0.00359 |
| Haiku 4.5 | $0.00000 | $0.00179 |
Grade A, and why
pr-sweep 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 1mo 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Sweep
A cross-repo PR sweep: discover → enrich → triage → review → act → report.
Announce at start: "I'm using the pr-sweep skill to sweep all open PRs."
Step 1: Discover All Open PRs
gh search prs \
--author @me \
--state open \
--json number,title,url,isDraft,repository,headRefName,baseRefName,reviewDecision \
--limit 100
Parse the result into a working list. Skip drafts immediately — they're not ready for action.
If you have more than 20 non-draft PRs, report the count and ask the user if they want to proceed or filter by repo.
Step 2: Enrich Each PR
For each non-draft PR, fetch CI and merge state in parallel (dispatch subagents or batch calls):
# CI status
gh pr checks <number> --repo <owner/repo> --json name,state,conclusion
# Merge state (up-to-date, behind, conflicting, etc.)
gh pr view <number> --repo <owner/repo> --json mergeStateStatus,mergeable
Build a status object per PR:
{
repo, number, title, url,
ciStatus: passing | failing | pending | none,
mergeState: clean | behind | dirty | blocked,
reviewDecision: APPROVED | CHANGES_REQUESTED | REVIEW_REQUIRED | null
}
Step 3: Triage
Classify each PR into one category (in priority order — first match wins):
| Category | Condition |
|---|---|
MERGE_READY |
CI passing, review approved or not required, merge state clean |
PENDING_CI |
CI still running, everything else clean |
NEEDS_REVIEW |
No reviews yet (reviewDecision null or REVIEW_REQUIRED) |
BEHIND_BASE |
Merge state is behind |
CI_FAILING |
CI has failed conclusions |
CHANGES_REQUESTED |
Reviewer has requested changes |
CONFLICTING |
Merge state is dirty (merge conflicts) |
BLOCKED |
Anything else preventing merge |
Show the triage table to the user and wait for confirmation before taking any action:
PR Triage
─────────────────────────────────────────────────────────────
MERGE_READY owner/repo #42 feat: add caching layer
NEEDS_REVIEW owner/repo #38 fix: auth token refresh
BEHIND_BASE other/repo #11 refactor: split service
CI_FAILING other/repo #9 feat: new export format
CHANGES_REQUESTED repo #7 fix: race condition
─────────────────────────────────────────────────────────────
Plan: merge 1, review 1, rebase 1, attempt CI fix 1, flag 1.
Proceed?
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.
- 1mo ago First seen · 215 lines · 0 tokens per session scan A a5df49b5995b
pr-sweep is a skill published in the GitHub repository harnessprotocol/harness-kit (10 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,795 tokens. 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
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
deploy-landed
A deployment verification procedure that checks whether the intended code revision is actually running, its environment settings are present, and the product works. A deployment is the process of putting new software on a server or hosting platform.
signing-preflight
Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…
triage
Triages a PR comment — from a bot (Copilot, CI) or a human reviewer. Routes to the triagehelper.py helper for identity checks, thread snapshotting, isolated-worktree fixes, and publish/reply/resolve mechanics; you classify the finding and apply a justified fix. --dry-run is fully read-only (investigation and a printed…
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…