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 zhinjs/zhin --skill github-accountgit clone --depth 1 https://github.com/zhinjs/zhinWrote 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/zhinjs/zhin/github-account)<a href="https://agentmods.dev/skills/zhinjs/zhin/github-account"><img src="https://agentmods.dev/badge/skills/zhinjs/zhin/github-account/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/zhinjs/zhin/github-account"><img src="https://agentmods.dev/badge/skills/zhinjs/zhin/github-account.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.00016 | $0.00157 |
| Opus 5.5 | $0.00006 | $0.00063 |
| Sonnet 5.5 | $0.00003 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
github-account 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 26d 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-account
处理 GitHub 身份与绑定状态时加载。bind 使用 Device Flow 绑定用户 OAuth 身份；install 返回 GitHub App 安装入口；whoami 用于确认当前绑定。用户想用自己的账号执行操作时先绑定。解绑和安装相关操作遵守 Tool 审批，不回显 Token、Device Code 或其他凭据。
What ships with it
5 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.
- 26d ago First seen · 21 lines · 16 tokens per session scan A 56906916fb57
github-account is a skill published in the GitHub repository zhinjs/zhin (136 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 157 once invoked, about $0.0001 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-09-21.
Other skills, from other repositories
Release Notes Generator
Generate professional software release notes from a commit log: classify changes, write user-facing summaries, draft a publishable announcement, and assess release readiness. Use for release, changelog, version, and deploy requests.
Market Research Brief
Generate a structured market research brief from a feature idea and supplied business context: market landscape, competitor intelligence, opportunity assessment, and a go-to-market recommendation. Use for market, research, competitor, and product launch requests.
pinned-release-checklist
Minimal guidance-only Skill used by release-pinned compatibility examples.
Release Checklist
Check release readiness and record a release note. Use for release and rollback requests.
Release Readiness Reviewer
Reviews a release candidate and produces a go/no-go readiness decision.
lobu-operator
Contribute safely to the Lobu monorepo: worktrees, package rules, red-to-green fixes, validation gates, SDK-first operations, PRs, and rollout checks.