Borrowing it
Nothing to install: this file belongs to dirien/yet-another-agent-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dirien/yet-another-agent-harness/main/.claude/skills/pull-request-msg/SKILL.mdgit clone --depth 1 https://github.com/dirien/yet-another-agent-harnessWrote 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/dirien/yet-another-agent-harness/pull-request-msg)<a href="https://agentmods.dev/skills/dirien/yet-another-agent-harness/pull-request-msg"><img src="https://agentmods.dev/badge/skills/dirien/yet-another-agent-harness/pull-request-msg/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/dirien/yet-another-agent-harness/pull-request-msg"><img src="https://agentmods.dev/badge/skills/dirien/yet-another-agent-harness/pull-request-msg.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00067 | $0.00976 |
| Opus 5.5 | $0.00027 | $0.00390 |
| Sonnet 5.5 | $0.00013 | $0.00195 |
| Haiku 4.5 | $0.00007 | $0.00098 |
Grade A, and why
pull-request-msg-with-gh 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Message Generator
Generate a PR_MESSAGE.md file summarizing the current session's work.
Requires gh CLI authenticated with the target repository.
Prerequisite check
gh --version 2>/dev/null && gh auth status 2>/dev/null
If gh is not installed, stop and report:
- Install from https://cli.github.com
ghcannot be installed via npm- After install, run
gh auth loginto authenticate
Do not proceed without a working, authenticated gh CLI.
Workflow
- Analyze session context — review changes made in the current
session. Explore changed files with
git diffandgit statusto understand the full scope of work, in addition to reviewing conversation history. Both sources inform the PR message. - Detect issue number — use the issue detection algorithm below.
If the user indicates there is no associated issue, omit the
Closes #<issue-number>footer entirely. - Determine commit type — based on the nature of changes (see
references/pr-message-format.mdfor the list of types) - Write PR_MESSAGE.md — using the format in
references/pr-message-format.md - Add to .gitignore — add
PR_MESSAGE.mdif not already present - Validate — run commitlint and markdownlint checks
Issue number detection
The issue number MUST be determined by searching GitHub, NOT by extracting numbers from branch names.
Algorithm
# Step 1: Get branch name
BRANCH=$(git branch --show-current)
# Step 2: Extract keywords (strip leading numbers and hyphens)
# Example: "125-greenops-equivalencies" → "greenops equivalencies"
KEYWORDS=$(echo "$BRANCH" | sed 's/^[0-9]*-//' | tr '-' ' ')
# Step 3: Search GitHub issues
gh issue list --search "$KEYWORDS" --state all \
--json number,title --limit 5
Evaluation rules
- Exactly 1 result with title containing most keywords → use it
- 0 results → ask the user for the issue number
- 2+ results → show options and ask the user to pick
- Ambiguous match → ask the user to confirm
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 · 119 lines · 67 tokens per session scan A 53f50f6c44a0
pull-request-msg-with-gh is a skill published in the GitHub repository dirien/yet-another-agent-harness (20 stars, last pushed 4mo ago), licensed MIT. It adds 67 tokens to every session and 976 once invoked, about $0.0003 per session on Opus 5.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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.