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 cisco-open/ai-harness-toolkit --skill create-pull-request-with-reviewersgit clone --depth 1 https://github.com/cisco-open/ai-harness-toolkitWrote 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/cisco-open/ai-harness-toolkit/create-pull-request-with-reviewers)<a href="https://agentmods.dev/skills/cisco-open/ai-harness-toolkit/create-pull-request-with-reviewers"><img src="https://agentmods.dev/badge/skills/cisco-open/ai-harness-toolkit/create-pull-request-with-reviewers/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/cisco-open/ai-harness-toolkit/create-pull-request-with-reviewers"><img src="https://agentmods.dev/badge/skills/cisco-open/ai-harness-toolkit/create-pull-request-with-reviewers.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.00051 | $0.01061 |
| Opus 5 | $0.00026 | $0.00531 |
| Sonnet 5 | $0.00010 | $0.00212 |
| Haiku 4.5 | $0.00005 | $0.00106 |
Grade A, and why
create-pull-request-with-reviewers 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request with Reviewers
Setup
Before using this skill, check if any metadata fields are empty strings. If any are empty:
- Prompt the user to provide the missing values (only prompt for fields that are empty):
repository: GitHub repository in format "org/repo"defaultReviewer: Default reviewer GitHub username to use if no reviewers found
- Update the SKILL.md frontmatter with the provided values so they don't need to configure again
Instructions
- Get Changed Files
Get files changed between current branch and main:
git diff --name-only origin/main...HEAD
- Analyze Git History for Reviewers
For each changed file, find contributors with commit counts and recency:
git log --format='%an|%ar' -- <file> | sort | uniq -c | sort -rn | head -10
Run this for each file from Step 1 to build per-file reviewer data.
- Get Eligible Collaborators
Get collaborators who can review:
gh api /repos/<metadata.repository>/collaborators --jq '.[].login'
Omit generic/service accounts (usernames matching common bot or service-account patterns).
- Get Current User
Get the current git user to exclude from reviewers:
git config user.name
- Rank Reviewers
- Match git history contributors with GitHub collaborators
- Exclude the current user (PR author) from recommendations
- Rank by number of commits to the affected files
- Select up to 3 reviewers (default to metadata.defaultReviewer if none found)
- Analyze Changes for PR Content
Understand the changes to generate PR details:
git log main..HEAD --oneline
git diff main...HEAD --stat
git diff main...HEAD
- Generate PR Details
Generate PR title using format: JIRA-KEY - Verb + description
Extract Jira keys from commit messages or branch name.
Generate description using this template:
## 🚀 Description, Motivation, and Context
<summary of changes>
## 📖 Issues and Related PRs
- [JIRA-KEY](<metadata.jiraBaseUrl>/browse/JIRA-KEY)
## 🌮 Required Items Complete:
- [ ] Unit tests written
- [ ] Integration tests written
- [ ] Coverage verified
- [ ] Functionally tested
- [ ] Deployable to production
- [ ] Uses feature flags
- [ ] README updated
- [ ] Build passes
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 · 163 lines · 51 tokens per session scan A 93732a2625b3
create-pull-request-with-reviewers is a skill published in the GitHub repository cisco-open/ai-harness-toolkit (11 stars, last pushed 13d ago), licensed Apache-2.0. It adds 51 tokens to every session and 1,061 once invoked, about $0.0003 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-31.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.