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/azure-samples/eshoplite/github-multi-accountnpx skills add Azure-Samples/eShopLite --skill github-multi-accountgit clone --depth 1 https://github.com/Azure-Samples/eShopLiteWhat 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.00043 | $0.01038 |
| Opus 5 | $0.00022 | $0.00519 |
| Sonnet 5 | $0.00009 | $0.00208 |
| Haiku 4.5 | $0.00004 | $0.00104 |
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 3d 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
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.
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
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.
- 3d ago First seen · 96 lines · 43 tokens per session scan A 8cdd19d1b4f4
github-multi-account is a skill published in the GitHub repository Azure-Samples/eShopLite (168 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,038 once invoked, about $0.0002 per session on Opus 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.
Other skills, from other repositories
foundry-agent-deploy
Build, register, and wire up a Foundry Hosted Agent end-to-end on Azure: build the container to ACR, register a hosted-agent version with the azure-ai-projects SDK, grant least-privilege RBAC, configure the CopilotKit runtime App Service, and verify through the Static Web App. Use when deploying or redeploying a…
foundry-hosted-agent-maf
Author a Microsoft Agent Framework (.NET) agent that is hosted as a Foundry Hosted Agent and speaks AG-UI over the invocations protocol. Use when building, refactoring, or reviewing a .NET agent that must run as a Foundry Hosted Agent and drive a CopilotKit / AG-UI frontend. WHEN: "build a Foundry hosted agent"…
mine
Mine a project or conversation into your MemPalace — extract and store memories for later retrieval.
status
Show MemPalace status — room counts, storage usage, and palace health.
mempalace-recall
Recall protocol for MemPalace — search the palace before answering about past work, people, projects, or prior decisions. Apply when the user asks what was decided, what happened before, who someone is, what was discussed last time, or anything that may already be filed in their memory palace; or when mempalace-recall…
multi-repo-release
Prepares and validates GPT-RAG umbrella releases across component repositories and the AI Landing Zone. Use for manifest pins, changelog entries, release branches, tags, and GitHub Release notes.