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.
npx agentmods add skills/ruvnet/ruflo/agent-github-modesnpx skills add ruvnet/ruflo --skill agent-github-modesgit clone --depth 1 https://github.com/ruvnet/rufloWhat 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.00021 | $0.01610 |
| Opus 5 | $0.00010 | $0.00805 |
| Sonnet 5 | $0.00004 | $0.00322 |
| Haiku 4.5 | $0.00002 | $0.00161 |
Grade A, and why
agent-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 2d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- agent-github-modes — 100% identical, 0 lines differ
- agent-github-modes — 100% identical, 0 lines differ
- agent-github-modes — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: github-modes description: Comprehensive GitHub integration modes for workflow orchestration, PR management, and repository coordination with batch optimization tools: mcp__claude-flow__swarm_init, mcp__claude-flow__agent_spawn, mcp__claude-flow__task_orchestrate, Bash, TodoWrite, Read, Write color: purple type: development capabilities:
- GitHub workflow orchestration
- Pull request management and review
- Issue tracking and coordination
- Release management and deployment
- Repository architecture and organization
- CI/CD pipeline coordination priority: medium hooks: pre: | echo "Starting github-modes..." echo "Initializing GitHub workflow coordination" gh auth status || (echo "GitHub CLI authentication required" && exit 1) git status > $dev$null || (echo "Not in a git repository" && exit 1) post: | echo "Completed github-modes" echo "GitHub operations synchronized" echo "Workflow coordination finalized"
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
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.
- 2d ago First seen · 178 lines · 21 tokens per session scan A 4bd2edb99590
agent-github-modes is a skill published in the GitHub repository ruvnet/ruflo (70,065 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 1,610 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
loop
Claude Code or Codex only. Drive a single feature — or a bounded milestone range of it — to completion by self-pacing /belmont:implement → verify → next → status until no pending milestones remain in range.
implement
Implement the next pending milestone from the PRD using the agent pipeline.
tech-plan
Technical planning session - create detailed implementation spec from PRD.
verify
Run verification and code review on completed tasks.
debug-manual
Manual debug loop with deep Belmont context and in-place spec reconciliation — user-verified fix + correct the specs that let the bug exist.
next
Implement just the next single pending task using the implementation agent.