A set of procedures for managing GitHub repositories through the `gh` command-line tool, including issues, pull requests, automated checks, releases, and security alerts.

It helps triage issues, review pull requests, investigate CI/CD failures, prepare releases and changelogs, and monitor contributor and security activity.

It gives repository maintenance a consistent process instead of making developers handle each issue, pull request, or failed check manually from scratch.

github-ops — Skill for Claude Code and Codex by JunMystery: A set of procedures for managing GitHub repositories through…

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.

agentmods

npx agentmods add skills/junmystery/agent-guidance-python/github-ops

Any agent

npx skills add JunMystery/Agent-Guidance-Python --skill github-ops

Clone the repo

git clone --depth 1 https://github.com/JunMystery/Agent-Guidance-Python

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/junmystery/agent-guidance-python/github-ops.svg)](https://agentmods.dev/skills/junmystery/agent-guidance-python/github-ops)

Your own site

<a href="https://agentmods.dev/skills/junmystery/agent-guidance-python/github-ops"><img src="https://agentmods.dev/badge/skills/junmystery/agent-guidance-python/github-ops.svg" alt="Measured on agentmods" height="20"></a>

Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,153 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 94% 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.

Model	Per session	Once invoked
Fable 5	$0.00071	$0.01153
Opus 5	$0.00036	$0.00576
Sonnet 5	$0.00014	$0.00231
Haiku 4.5	$0.00007	$0.00115

Measured yesterday against content hash 0688938f4d45, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-ops 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 yesterday.

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.

Origin

This is a copy

94% identical to github-ops — 29 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-ops/SKILL.md · 146 lines

How it starts

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

GitHub Operations

Manage GitHub repositories with a focus on community health, CI reliability, and contributor experience.

When to Activate

Triaging issues (classifying, labeling, responding, deduplicating)
Managing PRs (review status, CI checks, stale PRs, merge readiness)
Debugging CI/CD failures
Preparing releases and changelogs
Monitoring Dependabot and security alerts
Managing contributor experience on open-source projects
User says "check GitHub", "triage issues", "review PRs", "merge", "release", "CI is broken"

Tool Requirements

gh CLI for all GitHub API operations
Repository access configured via gh auth login

Issue Triage

Classify each issue by type and priority:

Types: bug, feature-request, question, documentation, enhancement, duplicate, invalid, good-first-issue

Priority: critical (breaking/security), high (significant impact), medium (nice to have), low (cosmetic)

Triage Workflow

Read the issue title, body, and comments
Check if it duplicates an existing issue (search by keywords)
Apply appropriate labels via gh issue edit --add-label
For questions: draft and post a helpful response
For bugs needing more info: ask for reproduction steps
For good first issues: add good-first-issue label
For duplicates: comment with link to original, add duplicate label

# Search for potential duplicates
gh issue list --search "keyword" --state all --limit 20

# Add labels
gh issue edit <number> --add-label "bug,high-priority"

# Comment on issue
gh issue comment <number> --body "Thanks for reporting. Could you share reproduction steps?"

PR Management

Review Checklist

Check CI status: gh pr checks <number>
Check if mergeable: gh pr view <number> --json mergeable
Check age and last activity
Flag PRs >5 days with no review
For community PRs: ensure they have tests and follow conventions

Stale Policy

Issues with no activity in 14+ days: add stale label, comment asking for update
PRs with no activity in 7+ days: comment asking if still active
Auto-close stale issues after 30 days with no response (add closed-stale label)

Read the full file on GitHub · 146 lines

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.

yesterday First seen · 146 lines · 71 tokens per session scan A 0688938f4d45

Subscribe to this mod's changes

github-ops is a skill published in the GitHub repository JunMystery/Agent-Guidance-Python (2 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,153 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to github-ops, differing in 29 lines, and is treated as a copy.

CI and CD DevOps and cloud Git and workflow Releases ai-agent coding-standards mcp-server software-development-workflow

publishing

Publishing and release workflow with semantic-release and GitHub Actions.

adeze/raindrop-mcp · 14 tokens

myco:monorepo-release-pipeline

Covers the full release pipeline for the unifi-mcp monorepo: determining release scope by analyzing changed packages, scoping hatch-vcs version tag globs per Python package to prevent sibling-tag contamination, pushing tags in strict dependency order (unifi-core → unifi-mcp-shared → app servers → relay → worker when…

sirkirby/unifi-mcp · 194 tokens

release-gate

Use when: user asks to push, tag, release, publish, create a version, validate synchronization, fix CI, inspect GitHub Actions, or make changes safe for GitHub. Runs the FFBB MCP Server release-readiness workflow, adapted from sickn33 skills lint-and-validate, verification-before-completion, git-pushing, iterate-pr…

nickdesi/FFBB-MCP-Server · 84 tokens

github-ops