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 techysy/yangyu-hermes-skills --skill github-repo-auditgit clone --depth 1 https://github.com/techysy/yangyu-hermes-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/techysy/yangyu-hermes-skills/github-repo-audit)<a href="https://agentmods.dev/skills/techysy/yangyu-hermes-skills/github-repo-audit"><img src="https://agentmods.dev/badge/skills/techysy/yangyu-hermes-skills/github-repo-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/techysy/yangyu-hermes-skills/github-repo-audit"><img src="https://agentmods.dev/badge/skills/techysy/yangyu-hermes-skills/github-repo-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.00118 | $0.04869 |
| Opus 5 | $0.00059 | $0.02434 |
| Sonnet 5 | $0.00024 | $0.00974 |
| Haiku 4.5 | $0.00012 | $0.00487 |
Grade A, and why
github-repo-audit scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
import zipfile, json, urllib.request The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
8 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.
- references/dead-component-and-upstream-alignment.md 2.6 KB
- references/navi-bookmarks-chrome-audit-v2.md 3.3 KB
- references/navi-bookmarks-chrome-audit-v3.md 2.0 KB
- references/navi-bookmarks-chrome-audit.md 6.0 KB
- references/readme-diagram-and-banner.md 2.4 KB
- references/structure-audit.md 4.4 KB
- references/version-badges.md 1.5 KB
- scripts/audit_repo.py 8.3 KB runs code
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.
- 10d ago First seen · 244 lines · 118 tokens per session scan A bcec75115c9e
github-repo-audit is a skill published in the GitHub repository techysy/yangyu-hermes-skills (5 stars, last pushed 16d ago), with no licence file. It adds 118 tokens to every session and 4,869 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
mx-pr
Draft a pull request from the feature spec and git log, run an autonomous commit-history cleanup (content check), then publish to GitHub or GitLab (Bitbucket experimental) — or hand off. Use when a feature branch is ready for PR, standalone or from mx-flow. Usage: /mx-pr [name].
breaking-change-audit
Audit shipctl's public interface before a release — compare flags, exit codes, and output formats against the previous tag to catch accidental breaking changes. Use when preparing a release, when asked to "check for breaking changes", or as a gate before tagging a new version.
git-conventional-commits
Author standardized conventional commit messages (feat, fix, docs, refactor, chore), generate automated semver releases, and format pull request descriptions.
github-profile-readme
Build or rewrite a GitHub profile README (the username/username special repo) with a personalized theme — animated SVG banner, stats cards, contribution snake, tech badges, project/research tables. Includes the git conflict pitfall when the local clone is stale vs GitHub web edits, and the PyYAML on: quirk for…
github-repo-management
Clone/create/fork repos; manage remotes, releases.
github-pr-workflow
Complete guide for managing the PR lifecycle. Each section shows the gh way first, then the git + curl fallback for machines without gh.