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/atlasomnia/hermes-custom-pack/github-authnpx skills add AtlasOmnia/hermes-custom-pack --skill github-authgit clone --depth 1 https://github.com/AtlasOmnia/hermes-custom-packWhat 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.00021 | $0.01710 |
| Opus 5 | $0.00010 | $0.00855 |
| Sonnet 5 | $0.00004 | $0.00342 |
| Haiku 4.5 | $0.00002 | $0.00171 |
Grade F, and why
github-auth scanned grade F with 4 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 2d 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.
Enumerates the file system for secretshighData exfiltration
Searching home directories for .env, .ssh, .aws or credential files is reconnaissance for credential theft.
ls -la ~/.ssh/id_*.pub 2>/dev/null || echo "No SSH keys found" Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
3. If `gh` is not installed → use "git-only" method below (no sudo needed) Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
ssh-keygen -t ed25519 -C "[email protected]" -f ~/.ssh/id_ed25519 -N "" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
When `gh` is not available, you can still access the full GitHub API using `curl` with a personal access token. This is how the other GitHub skills implement their fallbacks. This is a copy
80% identical to github-auth — 100 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Authentication Setup
This skill sets up authentication so the agent can work with GitHub repositories, PRs, issues, and CI. It covers two paths:
git(always available) — uses HTTPS personal access tokens or SSH keysghCLI (if installed) — richer GitHub API access with a simpler auth flow
Detection Flow
When a user asks you to work with GitHub, run this check first:
# Check what's available
git --version
gh --version 2>/dev/null || echo "gh not installed"
# Check if already authenticated
gh auth status 2>/dev/null || echo "gh not authenticated"
git config --global credential.helper 2>/dev/null || echo "no git credential helper"
Decision tree:
- If
gh auth statusshows authenticated → you're good, useghfor everything - If
ghis installed but not authenticated → use "gh auth" method below - If
ghis not installed → use "git-only" method below (no sudo needed)
Method 1: Git-Only Authentication (No gh, No sudo)
This works on any machine with git installed. No root access needed.
Option A: HTTPS with Personal Access Token (Recommended)
This is the most portable method — works everywhere, no SSH config needed.
Step 1: Create a personal access token
Tell the user to go to: https://github.com/settings/tokens
- Click "Generate new token (classic)"
- Give it a name like "hermes-agent"
- Select scopes:
repo(full repository access — read, write, push, PRs)workflow(trigger and manage GitHub Actions)read:org(if working with organization repos)- Set expiration (90 days is a good default)
- Copy the token — it won't be shown again
Step 2: Authenticate git — prefer the CLI or OS credential manager
# Recommended: log in with the GitHub CLI (token handled by gh/OS keychain)
gh auth login
# Or use git's built-in credential manager (macOS Keychain / Windows Credential Manager)
git config --global credential.helper osxkeychain # macOS
git config --global credential.helper manager # Windows
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.
- 2d ago First seen · 232 lines · 21 tokens per session scan F aa426cdc48d4
github-auth is a skill published in the GitHub repository AtlasOmnia/hermes-custom-pack (55 stars, last pushed 18d ago), licensed MIT. It adds 21 tokens to every session and 1,710 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it F with 4 findings (enumerates the file system for secrets, asks for root, reaches for credential files). It is 80% identical to github-auth, differing in 100 lines, and is treated as a copy.
Other skills, from other repositories
config
Use when configuring obshare-cli credentials, checking saved settings, testing connectivity, clearing local config, or setting optional Obsidian bridge values used by the V0.2.0 direct-share stack.
obshare-cli
Use when setting up obshare-cli 0.2.0, reviewing available commands, or choosing the right command for config, upload, permission, history, delete, and the plugin-first direct-share workflow.
permission
Use when changing Feishu document visibility, copy permissions, or download permissions for an uploaded document token.
upload
Use when uploading a Markdown note to Feishu, optionally applying public or copy/download permissions, or requesting JSON upload results for automation or the Obsidian plugin direct-share flow.
delete
Use when removing a Feishu document by token and cleaning the matching entry from local obshare-cli upload history.
list
Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.