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 skills add akhilyad/deployy --skill agent-github-modesgit clone --depth 1 https://github.com/akhilyad/deployyWrote 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.
[](https://agentmods.dev/skills/akhilyad/deployy/agent-github-modes)<a href="https://agentmods.dev/skills/akhilyad/deployy/agent-github-modes"><img src="https://agentmods.dev/badge/skills/akhilyad/deployy/agent-github-modes/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.
<a href="https://agentmods.dev/skills/akhilyad/deployy/agent-github-modes"><img src="https://agentmods.dev/badge/skills/akhilyad/deployy/agent-github-modes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00021 | $0.01601 |
| Opus 5.5 | $0.00008 | $0.00640 |
| Sonnet 5.5 | $0.00004 | $0.00320 |
| Haiku 4.5 | $0.00002 | $0.00160 |
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 14d 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.
This is a copy
92% identical to agent-github-modes — 14 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.
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__hyrex__swarm_init, mcp__hyrex__agent_spawn, mcp__hyrex__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 Hyrex 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
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.
- 14d ago First seen · 178 lines · 21 tokens per session scan A 1d674e3adc48
agent-github-modes is a skill published in the GitHub repository akhilyad/deployy (0 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 1,601 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to agent-github-modes, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.