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 adamjali/claude-skills --skill github-auditgit clone --depth 1 https://github.com/adamjali/claude-skillsWrote 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/adamjali/claude-skills/github-audit)<a href="https://agentmods.dev/skills/adamjali/claude-skills/github-audit"><img src="https://agentmods.dev/badge/skills/adamjali/claude-skills/github-audit/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/adamjali/claude-skills/github-audit"><img src="https://agentmods.dev/badge/skills/adamjali/claude-skills/github-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00057 | $0.01833 |
| Opus 5.5 | $0.00023 | $0.00733 |
| Sonnet 5.5 | $0.00011 | $0.00367 |
| Haiku 4.5 | $0.00006 | $0.00183 |
Grade A, and why
github-audit 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Audit
Comprehensive GitHub repo audit → auto-fix → quality gate → (confirmed) deploy → record.
Tracks decisions in .planning/github-audit-history.md for cross-run consistency.
allowed-toolsabove PRE-APPROVES safe/common tools (it does NOT restrict — every tool stays callable).git push,gh pr merge, and any deploy command are deliberately NOT pre-approved, and Phase 4 is gated by an explicit confirmation.
Run mode (from $ARGUMENTS)
$0 selects scope (default = full):
audit-only→ Phases 0, 1, 5 only. Report findings; make NO changes, NO deploy.fix→ Phases 0–3 + 5. Fix + quality gate; STOP before deploy.deployor empty → all phases (Phase 4 still requires the confirmation gate).
Execution rules
- Auto-fix only safe/small items that match a Saved Policy; otherwise STOP and discuss via
AskUserQuestion. - Quality gate: zero tolerance — fix ALL errors/warnings/failures (a known flaky test must pass in isolation to count as green).
- Deploy: sequential gates; each step must succeed before the next; never without the Phase 4 confirmation.
- Prefer a platform MCP/API over scraping CLI output when one is available (e.g. a hosting or backend MCP for deployment/env status).
Phase 0 — Initialize
- Read
.planning/github-audit-history.md(Saved Policies + last audits). If it has anIN_PROGRESSblock, ask the user to resume or start fresh. git remote -v,git branch --show-current. Deriveowner/repo.- Detect the project's toolchain (package manager + scripts) from
package.json, lockfiles,Makefile, or the CI config — don't assume one. Note the run mode. Record anIN_PROGRESSentry (timestamp + phase) in the history file.
Phase 1 — Audit (read-only; run checks in parallel)
- Security:
gh api repos/{o}/{r}/dependabot/alerts(open, by severity + package),.../code-scanning/alerts,.../secret-scanning/alerts. - CI/CD:
gh api .../actions/workflows+ recentgh run list; read each workflow YAML for stale matrices, missing perms, unpinned actions, broken auth secrets. - Branch protection:
gh api .../branches/{default}/protection— required checks, strict, enforce_admins, force-push/deletions, reviews. - PRs:
gh pr list --state open— categorize Dependabot (dev/patch = low, prod/major = high) vs human/bot. - Community:
gh api .../community/profile+ presence of SECURITY.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md, templates, README, LICENSE. - Traffic/activity: views/clones (flag anomalies), stars/forks, open issues.
- Config hygiene:
dependabot.ymlignore rules vs actual deps; linter ignore files; stale CI references.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 98 lines · 57 tokens per session scan A ab9880f80001
github-audit is a skill published in the GitHub repository adamjali/claude-skills (1 stars, last pushed 13d ago), licensed MIT. It adds 57 tokens to every session and 1,833 once invoked, about $0.0002 per session on Opus 5.5. 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-31.
Other skills, from other repositories
branch-recap
Takes stock of what a branch actually changed, before it gets pushed — works out the scope itself, then lays the change out group by group in one pass: files touched, what was done and why, how, and what deserves a second look, quoting code only where a remark needs it rather than reprinting the diffs. Closes on a…
slack-changelog
Turns what changed in a release into a Slack changelog a non-technical audience can read: filtered to what they would actually notice, one bullet per idea, plain language, no code vocabulary. Works out the scope itself across however many repositories sit in the working directory (a project can span several…
update-architecture-atlas
Create or refresh a versioned Curie architecture-atlas JSON snapshot from a git diff, including current and vision flows, maturity-rated seams, ADRs, and documentation drift. Use when asked to update, regenerate, compare, or add a version to the interactive architecture atlas.
commit-push-pr
Full git workflow - creates branch, commits, pushes, and creates or updates a PR with summary and test plan.
commit
Create a single well-crafted git commit from current changes. Analyzes diff, follows repo's commit style, and writes a concise "why not what" message.
github-activity
Report what happened across GitHub repositories over a time window, read only. Invoke when the user asks what merged, which issues were opened or closed, or what moved between milestones since a date or since the last report, across one or more repositories.