gh-auth-isolation

gh-auth-isolation is a skill for Claude Code, Codex from github/gh-aw. It costs 20 tokens per session (1,543 once invoked), scanned A, original, MIT.

A procedure for using separate GitHub identities safely, such as a company-managed account and a personal account. It checks the active account before GitHub operations and explains how to select the needed credentials.

In plain words
What is it for?
Use it to inspect GitHub login status, choose the correct account, and keep enterprise and personal repository work separate.
Why use it?
It helps prevent pushing code, opening pull requests, or accessing repositories with the wrong account.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

Good fit Use it to inspect GitHub login status, choose the correct account, and keep enterprise and personal repository work separate.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/github/gh-aw/gh-auth-isolation
About the project

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.

github/gh-aw · 5,421 stars · on GitHub · gh.io

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 github/gh-aw --skill gh-auth-isolation
Clone the repo
git clone --depth 1 https://github.com/github/gh-aw

Made for: Claude Code, Codex.

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.

agentmods badge for gh-auth-isolation

README.md
[![agentmods](https://agentmods.dev/badge/skills/github/gh-aw/gh-auth-isolation/github.svg)](https://agentmods.dev/skills/github/gh-aw/gh-auth-isolation)
Your own site
<a href="https://agentmods.dev/skills/github/gh-aw/gh-auth-isolation"><img src="https://agentmods.dev/badge/skills/github/gh-aw/gh-auth-isolation/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.

agentmods 80×15 button for gh-auth-isolation

Your own site · 80×15
<a href="https://agentmods.dev/skills/github/gh-aw/gh-auth-isolation"><img src="https://agentmods.dev/badge/skills/github/gh-aw/gh-auth-isolation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,543 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, 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 15
    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.
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.01543
Opus 5.5 $0.00008 $0.00617
Sonnet 5.5 $0.00004 $0.00309
Haiku 4.5 $0.00002 $0.00154

Measured 1mo ago against content hash 813f70bbad2b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gh-auth-isolation 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 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.

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

Copies of this mod

8 near-identical copies found in the catalogue:

.squad/templates/skills/gh-auth-isolation/SKILL.md · 184 lines

How it starts

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

Context

Many developers use GitHub through an Enterprise Managed User (EMU) account at work while maintaining a personal GitHub account for open-source contributions. AI agents spawned by Squad inherit the shell's default gh authentication — which is usually the EMU account. This causes failures when agents try to push to personal repos, create PRs on forks, or interact with resources outside the enterprise org.

This skill teaches agents how to detect the active identity, switch contexts safely, and avoid mixing credentials across operations.

Patterns

Detect Current Identity

Before any GitHub operation, check which account is active:

gh auth status

Look for:

  • Logged in to github.com as USERNAME — the active account
  • Token scopes: ... — what permissions are available
  • Multiple accounts will show separate entries

Extract a Specific Account's Token

When you need to operate as a specific user (not the default):

# Get the personal account token (by username)
gh auth token --user personaluser

# Get the EMU account token
gh auth token --user corpalias_enterprise

Use case: Push to a personal fork while the default gh auth is the EMU account.

Push to Personal Repos from EMU Shell

The most common scenario: your shell defaults to the EMU account, but you need to push to a personal GitHub repo.

# 1. Extract the personal token
$token = gh auth token --user personaluser

# 2. Push using token-authenticated HTTPS
git push https://personaluser:[email protected]/personaluser/repo.git branch-name

Why this works: gh auth token --user reads from gh's credential store without switching the active account. The token is used inline for a single operation and never persisted.

Create PRs on Personal Forks

When the default gh context is EMU but you need to create a PR from a personal fork:

# Option 1: Use --repo flag (works if token has access)
gh pr create --repo upstream/repo --head personaluser:branch --title "..." --body "..."

# Option 2: Temporarily set GH_TOKEN for one command
$env:GH_TOKEN = $(gh auth token --user personaluser)
gh pr create --repo upstream/repo --head personaluser:branch --title "..."
Remove-Item Env:\GH_TOKEN

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

  1. 1mo ago First seen · 184 lines · 20 tokens per session scan A 813f70bbad2b

Subscribe to this mod's changes

gh-auth-isolation is a skill published in the GitHub repository github/gh-aw (5,421 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,543 once invoked, about $0.0001 per session on Opus 5.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.