github-pr-workflow

github-pr-workflow is a skill for Claude Code, Codex from aivrar/portable-hermes-agent. It costs 20 tokens per session (2,901 once invoked), scanned D, a copy of github-pr-workflow, MIT.

A workflow for taking code changes from a Git branch through a GitHub pull request to review, continuous integration, and merging. Continuous integration, or CI, automatically checks proposed changes.

In plain words
What is it for?
Use it to create branches and commits, open pull requests, monitor checks, and merge approved work.
Why use it?
It keeps the steps from creating a branch to merging code in one consistent process and makes CI status visible.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create branches and commits, open pull requests, monitor checks, and merge approved work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aivrar/portable-hermes-agent/github-pr-workflow
Install

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.

Any agent
npx skills add aivrar/portable-hermes-agent --skill github-pr-workflow
Clone the repo
git clone --depth 1 https://github.com/aivrar/portable-hermes-agent

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for github-pr-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/aivrar/portable-hermes-agent/github-pr-workflow/github.svg)](https://agentmods.dev/skills/aivrar/portable-hermes-agent/github-pr-workflow)
Your own site
<a href="https://agentmods.dev/skills/aivrar/portable-hermes-agent/github-pr-workflow"><img src="https://agentmods.dev/badge/skills/aivrar/portable-hermes-agent/github-pr-workflow/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.

agentmods 80×15 button for github-pr-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/aivrar/portable-hermes-agent/github-pr-workflow"><img src="https://agentmods.dev/badge/skills/aivrar/portable-hermes-agent/github-pr-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,901 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 3 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 80% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.02901
Opus 5 $0.00010 $0.01451
Sonnet 5 $0.00004 $0.00580
Haiku 4.5 $0.00002 $0.00290

Measured 9d ago against content hash d752ffa2993c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade D, and why

github-pr-workflow scanned grade D with 3 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 9d 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

| Add comment | `gh pr comment N --body "..."` | `curl -X POST .../issues/N/comments -d '{"body":"..."}'` |

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

elif grep -q "github.com" ~/.git-credentials 2>/dev/null; then

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

Complete guide for managing the PR lifecycle. Each section shows the `gh` way first, then the `git` + `curl` fallback for machines without `gh`.
Origin

This is a copy

80% identical to github-pr-workflow — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/github/github-pr-workflow/SKILL.md · 368 lines

How it starts

The opening of the file, as written. The whole thing — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Pull Request Workflow

Complete guide for managing the PR lifecycle. Each section shows the gh way first, then the git + curl fallback for machines without gh.

Prerequisites

  • Authenticated with GitHub (see github-auth skill)
  • Inside a git repository with a GitHub remote

Quick Auth Detection

# Determine which method to use throughout this workflow
if command -v gh &>/dev/null && gh auth status &>/dev/null; then
  AUTH="gh"
else
  AUTH="git"
  # Ensure we have a token for API calls
  if [ -z "$GITHUB_TOKEN" ]; then
    if _hermes_env="${HERMES_HOME:-$HOME/.hermes}/.env"; [ -f "$_hermes_env" ] && grep -q "^GITHUB_TOKEN=" "$_hermes_env"; then
      GITHUB_TOKEN=$(grep "^GITHUB_TOKEN=" "$_hermes_env" | head -1 | cut -d= -f2 | tr -d '\n\r')
    elif grep -q "github.com" ~/.git-credentials 2>/dev/null; then
      GITHUB_TOKEN=$(uv run python "${HERMES_HOME:-$HOME/.hermes}/skills/github/github-auth/scripts/git-credential-token.py")
    fi
  fi
fi
echo "Using: $AUTH"

Extracting Owner/Repo from the Git Remote

Many curl commands need owner/repo. Extract it from the git remote:

# Works for both HTTPS and SSH remote URLs
REMOTE_URL=$(git remote get-url origin)
OWNER_REPO=$(echo "$REMOTE_URL" | sed -E 's|.*github\.com[:/]||; s|\.git$||')
OWNER=$(echo "$OWNER_REPO" | cut -d/ -f1)
REPO=$(echo "$OWNER_REPO" | cut -d/ -f2)
echo "Owner: $OWNER, Repo: $REPO"

1. Branch Creation

This part is pure git — identical either way:

# Make sure you're up to date
git fetch origin
git checkout main && git pull origin main

# Create and switch to a new branch
git checkout -b feat/add-user-authentication

Branch naming conventions:

  • feat/description — new features
  • fix/description — bug fixes
  • refactor/description — code restructuring
  • docs/description — documentation
  • ci/description — CI/CD changes

2. Making Commits

Use the agent's file tools (write_file, patch) to make changes, then commit:

Read the full file on GitHub · 368 lines

Files

What ships with it

4 files 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.

Changes

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.

  1. 9d ago First seen · 368 lines · 20 tokens per session scan D d752ffa2993c

Subscribe to this mod's changes

github-pr-workflow is a skill published in the GitHub repository aivrar/portable-hermes-agent (218 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 2,901 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 3 findings (sends data to an external url, reaches for credential files, makes network calls). It is 80% identical to github-pr-workflow, differing in 32 lines, and is treated as a copy.

Related

Other skills, from other repositories

devops-pipeline

Configure pre-commit hooks and lean GitHub Actions for shift-left quality assurance. Use when adding or auditing CI/CD to maximize local test coverage and minimize CI cost. Skip for Terraform/K8s, deployment pipelines, or non-GitHub CI providers.

luongnv89/skills · 56 tokens

git-commits-and-prs

Load BEFORE creating a git commit or a GitHub pull request. Step-by-step protocol for drafting commit messages, staging safely, amend rules, and gh pr create choreography.

sergezuber/FABULA-LLM-5 · 42 tokens

dependabot-consolidator

Consolidate a repository's open Dependabot PRs into one tested branch and PR, grouping by ecosystem and risk, verifying with baseline-diff gates, and closing out on operator approval. Use when a repo has multiple open Dependabot PRs to batch, when consolidating dependency bumps into a single reviewable PR, or when…

vinnie357/claude-skills · 85 tokens

shared-tooling-git-hooks

Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.

agents-inc/skills · 41 tokens

release-nyx

Ship a new nyx-local-ai release end to end — bump versions consistently, run the quality gates (typecheck, smoke tests, package), install locally, tag and push so CI publishes the installer artifacts. Use when the user asks to release, ship, publish, bump the version, or cut a new build of the extension.

sthamann/nyx-local-ai · 72 tokens

check-fix

Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.

juliusz-cwiakalski/agentic-delivery-os · 27 tokens