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 skills add aaronnat23/disp8ch --skill github-auth-setupgit clone --depth 1 https://github.com/aaronnat23/disp8chWrote 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.
[](https://agentmods.dev/skills/aaronnat23/disp8ch/github-auth-setup)<a href="https://agentmods.dev/skills/aaronnat23/disp8ch/github-auth-setup"><img src="https://agentmods.dev/badge/skills/aaronnat23/disp8ch/github-auth-setup/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.
<a href="https://agentmods.dev/skills/aaronnat23/disp8ch/github-auth-setup"><img src="https://agentmods.dev/badge/skills/aaronnat23/disp8ch/github-auth-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00177 |
| Opus 5.5 | $0.00000 | $0.00071 |
| Sonnet 5.5 | $0.00000 | $0.00035 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
github-auth-setup 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.
What it actually says
GitHub Auth Setup
Use this skill when the user needs GitHub access configured correctly before repo, issue, or PR workflows will work.
Use when
- GitHub actions are blocked by missing auth or missing repo defaults.
- The user needs a safe checklist for PAT or app-token setup.
- A repo-aware workflow should be made reliable before execution.
Workflow
- Confirm whether the task needs read-only repo access, issue/PR write access, or admin scopes.
- Keep the minimum required token scope explicit.
- Check the configured token path and any default owner/repo settings before blaming the workflow.
- Separate setup problems from permission problems.
- End with a small validation step that proves GitHub access works.
Deliverable
- Required token scope.
- Required config values.
- Validation step.
- Next fix if auth still fails.
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.
- 1mo ago First seen · 22 lines · 0 tokens per session scan A 8aeb21bf8c9d
github-auth-setup is a skill published in the GitHub repository aaronnat23/disp8ch (100 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 177 tokens. 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-08-30.
Other skills, from other repositories
apply-patch
Apply multi-file or tricky edits atomically with git apply instead of many fragile editfile calls. Use when changing several files at once or when editfile fails to match.
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
commit
Create git commits with good messages. Use when user says "commit", "create commit", or asks to commit changes.
public-plugin-packaging
Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.
release-notes
Write release notes for a tagged release — a business-impact summary of what changed for the user, plus a thanks section naming every contributor whose commits are in the release. Short by construction.
review-this-branch
Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the pass/fail checklist.