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 Kevin-Liu-01/Agent-Machines --skill prgit clone --depth 1 https://github.com/Kevin-Liu-01/Agent-MachinesWrote 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/kevin-liu-01/agent-machines/pr)<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/pr"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/pr/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/kevin-liu-01/agent-machines/pr"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/pr.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.00026 | $0.01020 |
| Opus 5 | $0.00013 | $0.00510 |
| Sonnet 5 | $0.00005 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
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 6d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context (auto-detected from HEAD)
- Current branch: !
git branch --show-current - Remote status: !
git status -sb | head -1
PR Template
Read .github/PULL_REQUEST_TEMPLATE.md and fill every section. The template is mandatory.
Do not free-form the PR body.
Rules
- PR title:
type(scope): description(conventional commit format, under 70 chars) - Target branch: first positional arg from
$ARGUMENTSif provided, otherwisedev - Source branch: if
--branch <name>is in$ARGUMENTS, use that branch for diff/log commands instead of HEAD. This is needed when the PR branch lives in a different worktree or the main repo checkout. - Push with
-uif needed - Use
gh pr createwith--body "$(cat <<'EOF' ... EOF)"for correct formatting - LOC check: if diff exceeds 200 changed lines (excluding generated files), warn the user and suggest splitting into stacked PRs
Reviewer Resolution
Before filling the Reviewers section, resolve ownership from CODEOWNERS and git history.
Step 1: CODEOWNERS lookup
Run this to find owners for every changed file:
git diff --name-only upstream/dev..<source-branch> | while read -r file; do
owner=""
while IFS= read -r line; do
line="${line%%#*}" # strip comments
[ -z "$(echo "$line" | tr -d '[:space:]')" ] && continue
pattern=$(echo "$line" | awk '{print $1}')
owners=$(echo "$line" | awk '{$1=""; print $0}' | xargs)
# convert CODEOWNERS glob to regex: /foo/ matches foo/anything, *.rs matches *.rs
case "$file" in
${pattern#/}*) owner="$owners" ;;
esac
done < .github/CODEOWNERS
echo "$owner"
done | tr ' ' '\n' | grep '^@' | sort | uniq -c | sort -rn
The top results are the CODEOWNERS-designated reviewers.
Step 2: blame-based context reviewers
Run this to find who recently touched the changed files (excluding the PR author):
author=$(git config user.name)
git diff --name-only upstream/dev..<source-branch> | head -20 | while read -r file; do
[ -f "$file" ] && git log --format='%aN' --since='3 months' -- "$file"
done | sort | uniq -c | sort -rn | grep -v "$author" | head -5
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.
- 6d ago First seen · 101 lines · 26 tokens per session scan A 00753ac09932
pr is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (27 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 1,020 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
smart-pr-generator
Analyzes Git diffs (staged or unstaged) and generates conventional commit messages and detailed, slop-free Pull Request descriptions.
engineering-git-workflow-master
A Git workflow guide covering branches, rebasing, worktrees, commit conventions, and branches that work well with continuous integration. Git is a system for tracking code changes.
gerrit-cli
Work with Gerrit code review from the terminal using the gerrit-cli binary - search changes, read diffs and inline comments, draft and publish review comments, add reviewers, set topic or WIP, abandon and revert. Use whenever the user mentions Gerrit, a CL or change number, a Change-Id, a gerrit. URL, a patchset, or…
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.