GitHub Agentic Workflows is a GitHub CLI extension that lets developers define AI-assisted repository automation in Markdown and run it through GitHub Actions. It is intended for tasks requiring interpretation or reasoning, such as issue triage, pull-request review, CI investigation, documentation maintenance, and dependency analysis. The catalogue entries provide skills and agents for working with these workflows.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/github/gh-awnpx agentmods add skills/github/gh-aw/cross-machine-coordinationWrote 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/github/gh-aw/cross-machine-coordination)<a href="https://agentmods.dev/skills/github/gh-aw/cross-machine-coordination"><img src="https://agentmods.dev/badge/skills/github/gh-aw/cross-machine-coordination/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/github/gh-aw/cross-machine-coordination"><img src="https://agentmods.dev/badge/skills/github/gh-aw/cross-machine-coordination.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 296 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Tool Misuse · line 321 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Privilege Escalation · line 323 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Excessive Agency · line 419 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.02855 |
| Opus 5.5 | $0.00008 | $0.01142 |
| Sonnet 5.5 | $0.00004 | $0.00571 |
| Haiku 4.5 | $0.00002 | $0.00285 |
Grade B, and why
cross-machine-coordination scanned grade B with 1 finding 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.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
FIX: Run: chmod 644 ~/.config/voice/model.yaml Copies of this mod
4 near-identical copies found in the catalogue:
- cross-machine-coordination — 100% identical, 10 lines differ
- cross-machine-coordination — 100% identical, 0 lines differ
- cross-machine-coordination — 92% identical, 8 lines differ
- cross-machine-coordination — 92% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 443 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Cross-Machine Coordination Pattern
Skill ID: cross-machine-coordination
Owner: Ralph (Work Monitor)
Squad Integration: All agents
Status: Specification (ready for implementation)
Overview
Enables squad agents running on different machines (laptop, DevBox, Azure VM) to securely share work, coordinate execution, and pass results without manual intervention.
Pattern: Git-based task queuing + GitHub Issues supplement
Usage
For Task Sources (Orchestrating Machine)
To assign work to DevBox:
# Create task file
cat > .squad/cross-machine/tasks/2026-03-14T1530Z-laptop-gpu-voice-clone.yaml << 'EOF'
id: gpu-voice-clone-001
source_machine: laptop-machine
target_machine: devbox
priority: high
created_at: 2026-03-14T15:30:00Z
task_type: gpu_workload
payload:
command: "python scripts/voice-clone.py --input voice.wav --output cloned.wav"
expected_duration_min: 15
resources:
gpu: true
memory_gb: 8
status: pending
EOF
# Commit & push
git add .squad/cross-machine/tasks/
git commit -m "Cross-machine task: GPU voice cloning [squad:machine-devbox]"
git push origin main
Ralph on DevBox will:
- Pull the task on next cycle (5-10 min)
- Validate schema & command whitelist
- Execute the GPU workload
- Write result to
.squad/cross-machine/results/gpu-voice-clone-001.yaml - Commit & push the result
For Task Executors (DevBox, Azure VMs)
Ralph automatically watches .squad/cross-machine/tasks/ for work targeted at this machine.
On each cycle (5-10 min):
# Pseudo-code (Ralph implementation)
1. git pull origin main
2. Load all .yaml files in .squad/cross-machine/tasks/
3. Filter for status=pending AND target_machine=HOSTNAME
4. For each task:
a. Validate schema (must have: id, source_machine, target_machine, payload)
b. Validate command against whitelist
c. Execute task (with timeout)
d. Write result to .squad/cross-machine/results/{id}.yaml
e. Commit & push result
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.
- 1mo ago First seen · 443 lines · 21 tokens per session scan B 2c31feb5a668
cross-machine-coordination is a skill published in the GitHub repository github/gh-aw (5,435 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 2,855 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
c-github
Interact with GitHub using the gh CLI and jq. Manage PRs, issues, repositories, and Actions workflows. Make raw API calls with gh api for anything not covered by built-in commands.
watch-pr
Watch a GitHub pull request for CI status, reviews, comments, merge conflicts, and terminal states using the gh-watch extension. Use when the user wants to monitor a PR, wait for CI, or track PR progress.
watch-tag
Watch a GitHub repository for new tags using the gh-watch extension. Use when the user wants to be notified when a tag is created, when a release is cut, or when a tag that includes a specific commit appears (e.g. "tell me when my merge ships in a release").
watch-branch
Watch a GitHub branch for new commits using the gh-watch extension. Use when the user wants to be notified when new commits are pushed to a branch, monitor main for merges, or track branch activity.
ci-cd
CI/CD pipelines for GitHub Actions and Docker-based deployments — lint, test, build, push, deploy stages; environment secrets; branch-gated workflows; health-check rollbacks; and PM2/systemd service restarts.
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries.