github-auth SKILL.md skillB
github-auth from ethosagent/ethos is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ethosagent/ethos/github-auth@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ethosagent/ethos
- Path
skills/github/github-auth/SKILL.md- Versions recorded
- 3
- Latest version
- v1.0.0, committed Sep 25, 2026
- First version recorded
- Jun 1, 2026
- Size
- 6,859 bytes
- Repository stars
- 23
- License
- MIT
Operator setup for GitHub auth — HTTPS tokens (PAT, fine-grained, classic), SSH keys (ed25519), and `gh` CLI login. Diagnoses the common failure modes ("Permission denied", "Bad credentials", "Token expired") and walks the user to a working `git push` + `gh auth status`.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# GitHub Auth Get the operator's machine talking to GitHub. Three credential paths exist — pick the right one and stop. ## When to use this skill - `gh auth status` reports "not logged in" or "expired token". - `git push` returns "Permission denied (publickey)" or "fatal: Authentication failed". - User says "set up GitHub" / "configure git" on a fresh machine or fresh repo. ## When NOT to use this skill - The error is repo-level (branch protection, missing collaborator access) — that's a permissions problem on github.com, not a credential problem here. - The user is using GitHub Enterprise Server — the flows differ; ask before running `gh auth login`. ## Step 1 — diagnose Run these and read the output before doing anything: ```bash gh auth status git config --get remote.origin.url # capture: https://... or git@github.com:... ssh -T git@github.com 2>&1 | head -5 # for SSH paths ``` The current `remote.origin.url` tells you which path to fix. Don't switch the user from HTTPS to SSH (or vice versa) without asking — they may have habits or scripts that depend on the choice. ## Step 2 — pick the credential path ### Path A — `gh` CLI (recommended for most operators) …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_uwekoxco7kzdgs2t/8787b7dfae612412344bc229afb1316ad9276f26e7d98eeeb4a3296eac51f7de.json
Then /plugin install github-auth@markdownregistry-uwekoxco7kzdgs2t in Claude Code. It installs v1.0.0, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add ethosagent/ethos/github-auth@sha256:8787b7dfae612412The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_uwekoxco7kzdgs2t)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in ethosagent/ethos/github-auth since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of github-auth from somewhere else? Ask it: where did my github-auth come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 3 versions of this file, between Jun 1, 2026 and Sep 25, 2026, about one every 58 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-09-25 | 8b46a22 | 6,859 B | B | view · diff |
| v1.0.0 | 2026-06-05 | 74e845f | 6,678 B | B | view · diff |
| v1.0.0 | 2026-06-01 | a929618 | 6,640 B | B | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/github-auth/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- fail: No instruction to read or print local credentials (matched: cat ~/.ssh)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6859 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
ethosagent/ethos · 23 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uwekoxco7kzdgs2t GET https://markdownregistry.com/api/v1/resolve?ref=ethosagent/ethos/github-auth GET https://markdownregistry.com/api/v1/blob/8787b7dfae612412344bc229afb1316ad9276f26e7d98eeeb4a3296eac51f7de
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from ethosagent/ethos
Every file in ethosagent/ethos