github-multi-account

github-multi-account is a skill for Claude Code, Codex from Azure-Samples/eShopLite. It costs 43 tokens per session (1,038 once invoked), scanned A, a copy of github-multi-account, MIT.

A setup helper for people who use more than one GitHub account on the same computer. It detects the accounts signed in through GitHub's command-line tool and creates separate commands for personal and work use.

In plain words
What is it for?
Setting up personal and work GitHub account shortcuts after identifying which username belongs to each account.
Why use it?
It prevents commands from being sent through the wrong GitHub account. It also avoids repeatedly switching accounts by hand.

Skill for Claude CodeCodex

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

Good fit Setting up personal and work GitHub account shortcuts after identifying which username belongs to each account.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/azure-samples/eshoplite/github-multi-account
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 Azure-Samples/eShopLite --skill github-multi-account
Clone the repo
git clone --depth 1 https://github.com/Azure-Samples/eShopLite

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 github-multi-account

README.md
[![agentmods](https://agentmods.dev/badge/skills/azure-samples/eshoplite/github-multi-account/github.svg)](https://agentmods.dev/skills/azure-samples/eshoplite/github-multi-account)
Your own site
<a href="https://agentmods.dev/skills/azure-samples/eshoplite/github-multi-account"><img src="https://agentmods.dev/badge/skills/azure-samples/eshoplite/github-multi-account/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 github-multi-account

Your own site · 80×15
<a href="https://agentmods.dev/skills/azure-samples/eshoplite/github-multi-account"><img src="https://agentmods.dev/badge/skills/azure-samples/eshoplite/github-multi-account.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,038 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.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.01038
Opus 5.5 $0.00017 $0.00415
Sonnet 5.5 $0.00009 $0.00208
Haiku 4.5 $0.00004 $0.00104

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

Security

Grade A, and why

github-multi-account 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

This is a copy

100% identical to github-multi-account — 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.

.squad/templates/skills/github-multi-account/SKILL.md · 96 lines

How it starts

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

GitHub Multi-Account — AI-Driven Setup

When to Activate

When the user has multiple GitHub accounts (check with gh auth status). If you see 2+ accounts listed, this skill applies.

What to Do (as the AI agent)

Step 1: Detect accounts

Run: gh auth status Look for multiple accounts. Note which usernames are listed.

Step 2: Ask the user

Ask: "I see you have multiple GitHub accounts: {list them}. Which one is your personal account and which is your work/EMU account?"

Step 3: Run the setup automatically

Once the user confirms, do ALL of this for them:

# 1. Define the functions
$personal = "THEIR_PERSONAL_USERNAME"
$work = "THEIR_WORK_USERNAME"

# 2. Add to PowerShell profile
$profilePath = $PROFILE.CurrentUserAllHosts
if (!(Test-Path $profilePath)) { New-Item -Path $profilePath -Force | Out-Null }
$existing = Get-Content $profilePath -Raw -ErrorAction SilentlyContinue
if ($existing -notmatch "gh-personal") {
    $block = @"

# === GitHub Multi-Account Aliases ===
function gh-personal { gh auth switch --user $personal 2>`$null | Out-Null; gh @args }
function gh-work { gh auth switch --user $work 2>`$null | Out-Null; gh @args }
Set-Alias ghp gh-personal
Set-Alias ghw gh-work
"@
    Add-Content -Path $profilePath -Value $block
}

# 3. Create CMD wrappers
$binDir = Join-Path $env:USERPROFILE ".squad\bin"
if (!(Test-Path $binDir)) { New-Item -ItemType Directory -Path $binDir -Force | Out-Null }
"@echo off`ngh auth switch --user $personal >nul 2>&1`ngh %*" | Out-File "$binDir\ghp.cmd" -Encoding ascii
"@echo off`ngh auth switch --user $work >nul 2>&1`ngh %*" | Out-File "$binDir\ghw.cmd" -Encoding ascii

# 4. Add to PATH
$userPath = [Environment]::GetEnvironmentVariable("PATH", "User")
if ($userPath -notmatch [regex]::Escape($binDir)) {
    [Environment]::SetEnvironmentVariable("PATH", "$binDir;$userPath", "User")
    $env:PATH = "$binDir;$env:PATH"
}

# 5. Load in current session
function gh-personal { gh auth switch --user $personal 2>$null | Out-Null; gh @args }
function gh-work { gh auth switch --user $work 2>$null | Out-Null; gh @args }
Set-Alias ghp gh-personal
Set-Alias ghw gh-work

Read the full file on GitHub · 96 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 · 96 lines · 43 tokens per session scan A 8cdd19d1b4f4

Subscribe to this mod's changes

github-multi-account is a skill published in the GitHub repository Azure-Samples/eShopLite (168 stars, last pushed 7d ago), licensed MIT. It adds 43 tokens to every session and 1,038 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to github-multi-account, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

multi-repo-release

Prepares and validates GPT-RAG umbrella and multi-repository releases. Use whenever work involves release preparation, semantic versions, release branches, manifest or component pins, changelog release entries, tags, GitHub Release notes, or AI Landing Zone release alignment.

Azure/GPT-RAG · 56 tokens

zen-comprehensive-review

Orchestrate a multi-model code review: spawn 3 review subagents, merge findings. In PR mode, posts GitHub PR comments with reactions. In local mode, outputs findings directly. CRITICAL: this skill is costly, don't use it unless user explicitly requested to use it.

EliasOulkadi/shokunin · 63 tokens

git-workflow

Automate the complete Git development workflow — create feature branches with conventional naming, atomic commits with conventional commit messages, interactive rebase, squash merges, PR body generation from commit history, branch cleanup, and git worktree patterns. Use when user asks to create a branch, commit…

EliasOulkadi/shokunin · 107 tokens

portfolio-auto

Auto-sync GitHub repos to portfolio website. Scans GitHub repos, captures screenshots with Playwright, generates project entries, and updates projects-data.js or Supabase DB. Use when user asks to "update portfolio", "sync projects", "add my repos to portfolio", or "refresh portfolio projects". Do NOT use for one-time…

EliasOulkadi/shokunin · 77 tokens

gsd-forensics

Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong.

SpillwaveSolutions/agent-brain · 29 tokens

gsd-new-workspace

Create an isolated workspace with repo copies and independent .planning/.

SpillwaveSolutions/agent-brain · 18 tokens