agentmods.dev

github-workflows

github-workflows is a skill for Claude Code, Codex from dirtybits/agent-skills. It costs 41 tokens per session (2,176 once invoked), scanned A, original, MIT.

A workflow for handling GitHub repository work from start to finish, including authentication, issues, pull requests, code review, continuous integration checks, and releases.

In plain words
What is it for?
Use it to clone or fork repositories, manage issues and pull requests, review code, investigate failed GitHub Actions checks, and prepare or merge releases.
Why use it?
It gives coding agents a consistent way to inspect and change GitHub projects while checking access and repository state before making changes.

Skill for Claude CodeCodex

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

not rated 2repo 1mo ago A scan 41 tokens original MIT

Good fit Use it to clone or fork repositories, manage issues and pull requests, review code, investigate failed GitHub Actions checks, and prepare or merge releases.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dirtybits/agent-skills/github-workflows
View source ↗ dirtybits/agent-skills
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 dirtybits/agent-skills --skill github-workflows
Clone the repo
git clone --depth 1 https://github.com/dirtybits/agent-skills

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-workflows

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/dirtybits/agent-skills/github-workflows"><img src="https://agentmods.dev/badge/skills/dirtybits/agent-skills/github-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,176 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.00041 $0.02176
Opus 5.5 $0.00016 $0.00870
Sonnet 5.5 $0.00008 $0.00435
Haiku 4.5 $0.00004 $0.00218

Measured 1mo ago against content hash df2c6f030d3e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

github-workflows 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.

The scan reads SKILL.md. This mod also ships 1 executable file (references/absorbed-packages/github-auth/scripts/gh-env.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/github-workflows/SKILL.md · 119 lines

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.

GitHub Workflows

Overview

This umbrella replaces narrow GitHub skills with one class-level workflow. Load it whenever the task involves GitHub state or Git repository work that will touch GitHub: authentication, cloning/forking, issues, PRs, code review, CI, releases, or API fallbacks.

Prefer the gh CLI when authenticated. Fall back to git plus GitHub REST/GraphQL with $GITHUB_TOKEN when gh is missing or lacks a scope.

When to Use

  • Set up or troubleshoot GitHub auth.
  • Clone, fork, create, or inspect repositories.
  • Create, triage, label, or comment on issues.
  • Implement work on a branch and open/update/merge a PR.
  • Review a PR or request a pre-commit review before pushing.
  • Inspect codebase size/languages before planning repository work.
  • Diagnose or monitor GitHub Actions / CI failures.

Do not use for generic local debugging unless GitHub state matters; use systematic-debugging or the software-development umbrella for pure local work.

Operating Pattern

  1. Discover repository context. Run git remote -v, git status --short --branch, and derive OWNER/REPO from the GitHub remote.
  2. Check auth before side effects. Prefer gh auth status; otherwise locate $GITHUB_TOKEN from the environment or ~/.hermes/.env. Never claim a push/PR/comment happened until the command returns a URL or status.
  3. Search before creating. Search existing issues and PRs for duplicates before opening new maintainer-visible artifacts.
  4. Make minimal, reviewable changes. Use a branch, conventional commits, and a clear PR body with summary + tests.
  5. Verify with real outputs. Run tests locally when possible, inspect CI status/logs, and report exact URLs/IDs.
  6. Escalate permission blockers honestly. If PAT scopes, fork permissions, or branch protections block the action, leave the branch/patch ready and explain the failed command.

Labeled Subsections from Former Narrow Skills

Auth and credentials

  • gh auth status is the fastest readiness check, but success does not guarantee push/fork/createPullRequest scopes.
  • For REST fallback, extract GITHUB_TOKEN from the environment, Hermes .env, or git credentials only for the current command context; avoid printing secrets.
  • If direct push returns 403 or fork creation says Resource not accessible by personal access token, diagnose scopes instead of retrying blindly.

Read the full file on GitHub · 119 lines

Files

What ships with it

19 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. 1mo ago First seen · 119 lines · 41 tokens per session scan A df2c6f030d3e

Subscribe to this mod's changes

github-workflows is a skill published in the GitHub repository dirtybits/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 2,176 once invoked, about $0.0002 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-31.

CI and CDDevOps and cloudGit and workflowReleasescigithubpull-requestsworkflow
Related

Other skills, from other repositories

github-release-management

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.

ruvnet/RuView · 27 tokens

github-cli

A command-line tool connection for GitHub tasks that built-in tools do not cover. It uses GitHub's command-line program to work with issues, pull requests, releases, workflows, searches, and the GitHub API.

zhinjs/zhin · 30 tokens

github-release-management

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.

ruvnet/ruflo · 27 tokens

github-repo-care

Protocol for safely creating, publishing, releasing, auditing, and maintaining GitHub repositories: check local rules and locks, create .gitignore before the first add, run privacy checks, prepare README/i18n/banner/metadata, verify release tags and GitHub releases, and update organization profiles, llms.txt files…

ellmos-ai/skills · 72 tokens

publish-github-release

Use this whenever the user asks to ship, publish, release, tag, or cut a new version of the project — OR when CHANGELOG.md has an "Unreleased" / in-progress section ready to be shipped. The skill bumps the version across all version-bearing files, regenerates the CHANGELOG entry from git log since the last tag…

iampantherr/SecureContext · 99 tokens

github-release-management

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.

ruvnet/agentic-flow · 27 tokens