A command-line tool for managing GitHub work, including issues, pull requests, repositories, releases, and automated checks. GitHub is a service for hosting code and collaborating on software projects.

Use it to inspect or manage issues, pull requests, branches, releases, and CI runs, where CI means automated build and test checks.

It lets an agent handle routine GitHub tasks from the terminal and use the same workflow across repositories.

github-ops — Skill for Claude Code by ARCASSystems

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 ARCASSystems/FounderOS --skill github-ops

Clone the repo

git clone --depth 1 https://github.com/ARCASSystems/FounderOS

Made for: Claude Code.

Or install founder-os, the plugin that ships this one along with the rest of its 95 skills, 45 commands, 6 hooks.

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/arcassystems/founderos/github-ops/github.svg)](https://agentmods.dev/skills/arcassystems/founderos/github-ops)

Your own site

<a href="https://agentmods.dev/skills/arcassystems/founderos/github-ops"><img src="https://agentmods.dev/badge/skills/arcassystems/founderos/github-ops/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/arcassystems/founderos/github-ops"><img src="https://agentmods.dev/badge/skills/arcassystems/founderos/github-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,104 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.

Model	Per session	Once invoked
Fable 5.1	$0.00067	$0.01104
Opus 5	$0.00034	$0.00552
Sonnet 5	$0.00013	$0.00221
Haiku 4.5	$0.00007	$0.00110

Measured 5d ago against content hash b899e5454a66, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 5d 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.

skills/github-ops/SKILL.md · 87 lines

How it starts

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

GitHub Operations

Runs on: local-exec - runs a local script; on a cloud surface I read the results, I do not run it.

Fast GitHub operations on any repo your gh CLI is authenticated against.

Trigger

When the operator asks about GitHub issues, PRs, repos, actions, or releases.

Interface: gh CLI is canonical

Use the gh CLI via Bash for all read and write operations: gh issue list, gh pr view, gh api, gh run list, and so on. The CLI is the canonical interface for this skill.

A GitHub MCP server, if present in the session, may expose only authenticate and complete_authentication (auth-only) and not the full issue, PR, or Actions tool surface. Do not assume MCP covers an operation. Check the available tools at session start before relying on MCP, and fall back to gh whenever MCP does not cover what you need. If a future session has a fuller GitHub MCP wired up, prefer those tools and fall back to gh only for gaps.

Pre-flight

Confirm gh is installed and authenticated: gh auth status. If it is not, tell the operator to run gh auth login and stop.
Confirm the target repo. If the working directory is a git repo, gh infers it. For another repo, pass --repo owner/name explicitly.

Capabilities

Issues

Create issues: gh issue create --title "..." --body "..."
List and filter open issues: gh issue list --state open
Comment on issues: gh issue comment <number> --body "..."
Close or label issues: gh issue close <number>, gh issue edit <number> --add-label "..."

Pull requests

List open PRs: gh pr list --state open
Review PR diffs and comments: gh pr view <number> --comments, gh pr diff <number>
Create PRs (only when explicitly asked): gh pr create --title "..." --body "..."
Check PR CI status: gh pr checks <number>

Actions and CI

View recent workflow runs: gh run list
Check a specific run status and logs: gh run view <run-id> --log
Re-trigger a failed run (only when explicitly asked): gh run rerun <run-id>

Read the full file on GitHub · 87 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.

5d ago First seen · 87 lines · 67 tokens per session scan A b899e5454a66

Subscribe to this mod's changes

github-ops is a skill published in the GitHub repository ARCASSystems/FounderOS (5 stars, last pushed 25d ago), licensed MIT. It adds 67 tokens to every session and 1,104 once invoked, about $0.0003 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.

Claude Code Commits Git and workflow Project management Releases ai-agents founder-os llms-txt markdown operating-system

close-task-commit-push-pr

Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.

devoxx/DevoxxGenieIDEAPlugin · 64 tokens

ct-dev-workflow

Development workflow orchestration for task-driven development with atomic commits, conventional commit messages, and systematic release processes. Enforces task traceability, branch discipline, smart test scope selection, and GitHub Actions integration. Use when committing code, creating releases, managing branches…

kryptobaseddev/cleo · 76 tokens

github-ops