What is github-modes?

A set of commands for managing GitHub work in coordinated modes, such as handling pull requests, issues, and multi-repository tasks. GitHub is a service where developers store code and review changes.

Use it to coordinate complex GitHub tasks, manage pull requests, track issues, and work across multiple repositories.

It organizes different GitHub workflows so you do not have to manage each step manually. It is intended to help coordinate several related operations or agents.

github-modes — Command by f-amine

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 commands/f-amine/vibe-stack/github-modes

Clone the repo

git clone --depth 1 https://github.com/f-amine/vibe-stack

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan A 0 findings. Scan, not verified.

Origin 100% 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.00000	$0.01354
Opus 5	$0.00000	$0.00677
Sonnet 5	$0.00000	$0.00271
Haiku 4.5	$0.00000	$0.00135

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

Security

Grade A, and why

github-modes 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

100% identical to github-modes — 0 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.

.claude/commands/github/github-modes.md · 147 lines

How it starts

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

GitHub Integration Modes

Overview

This document describes all GitHub integration modes available in Claude-Flow with ruv-swarm coordination. Each mode is optimized for specific GitHub workflows and includes batch tool integration for maximum efficiency.

GitHub Workflow Modes

gh-coordinator

GitHub workflow orchestration and coordination

Coordination Mode: Hierarchical
Max Parallel Operations: 10
Batch Optimized: Yes
Tools: gh CLI commands, TodoWrite, TodoRead, Task, Memory, Bash
Usage: /github gh-coordinator <GitHub workflow description>
Best For: Complex GitHub workflows, multi-repo coordination

pr-manager

Pull request management and review coordination

Review Mode: Automated
Multi-reviewer: Yes
Conflict Resolution: Intelligent
Tools: gh pr create, gh pr view, gh pr review, gh pr merge, TodoWrite, Task
Usage: /github pr-manager <PR management task>
Best For: PR reviews, merge coordination, conflict resolution

issue-tracker

Issue management and project coordination

Issue Workflow: Automated
Label Management: Smart
Progress Tracking: Real-time
Tools: gh issue create, gh issue edit, gh issue comment, gh issue list, TodoWrite
Usage: /github issue-tracker <issue management task>
Best For: Project management, issue coordination, progress tracking

release-manager

Release coordination and deployment

Release Pipeline: Automated
Versioning: Semantic
Deployment: Multi-stage
Tools: gh pr create, gh pr merge, gh release create, Bash, TodoWrite
Usage: /github release-manager <release task>
Best For: Release management, version coordination, deployment pipelines

Repository Management Modes

repo-architect

Repository structure and organization

Structure Optimization: Yes
Multi-repo: Support
Template Management: Advanced
Tools: gh repo create, gh repo clone, git commands, Write, Read, Bash
Usage: /github repo-architect <repository management task>
Best For: Repository setup, structure optimization, multi-repo management

Read the full file on GitHub · 147 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 · 147 lines · 0 tokens per session scan A 622955b84aa0

Subscribe to this mod's changes

github-modes is a command published in the GitHub repository f-amine/vibe-stack (21 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,354 tokens. A static security scan graded it A with 0 findings. It is 100% identical to github-modes, differing in 0 lines, and is treated as a copy.

Code review Frontend Security ai better-auth claude claude-code drizzle-orm nextjs

github-modes