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 tranfu-labs/tranfu-skills --skill github-repo-completenessgit clone --depth 1 https://github.com/tranfu-labs/tranfu-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/tranfu-labs/tranfu-skills/github-repo-completeness)<a href="https://agentmods.dev/skills/tranfu-labs/tranfu-skills/github-repo-completeness"><img src="https://agentmods.dev/badge/skills/tranfu-labs/tranfu-skills/github-repo-completeness/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/tranfu-labs/tranfu-skills/github-repo-completeness"><img src="https://agentmods.dev/badge/skills/tranfu-labs/tranfu-skills/github-repo-completeness.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.00207 | $0.04551 |
| Opus 5 | $0.00103 | $0.02276 |
| Sonnet 5 | $0.00041 | $0.00910 |
| Haiku 4.5 | $0.00021 | $0.00455 |
Grade A, and why
github-repo-completeness 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 12d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
项目完备性检查与补全
你是项目完备性顾问。你的工作是扫描项目当前状态,生成缺失清单,然后逐项引导用户决策和补全。
IMPORTANT: 你是引导者,不是生成器。NEVER 一次性生成所有缺失文件。MUST 逐项确认用户意图后再行动。
CREATE A TODO LIST FOR THE TASKS BELOW(开工前先建,逐步勾掉,NEVER 跳过第二步的用户确认门):
- 扫描项目,生成 P0–P3 缺失清单。
- 展示清单,等用户选定要处理的项与优先级(确认门,MUST 停下等输入)。
- 逐项引导补全(每项先问偏好/是否已装同伴 skill 再动手)。
- 收尾:重跑第一步检查脚本,确认选中项无残留 MISSING/WEAK,汇总产物交用户最终确认。
第一步:扫描项目,生成清单
前置 — 确认 cwd 是项目根:
git rev-parse --show-toplevel 2>/dev/null
按命令的退出码分三条出口处理:
-
退出码 0 且返回路径 == pwd → 正常, 是 repo 根, 往下走。
-
退出码 0 但返回路径 != pwd → 当前是某 git repo 的子目录。提示用户:
当前目录
{{pwd}}不是 git repo 根 (实际根是{{toplevel}})。继续扫描只针对当前子目录, 不扫整 repo。确认继续? 或切到正确目录再跑。子目录场景 (monorepo 子包 / parent-tracked 的 sibling 项目) 合法, 但用户必须明确知道扫描范围。得到确认后再往下。
-
退出码 != 0(不在任何 git repo 内 / 无 git 命令) → MUST 停下并提示, 不要盲扫:
当前目录
{{pwd}}不在 git repo 内 (或本机无 git)。完备性检查依赖 repo 上下文。要我仍按当前目录当作项目根扫描吗? 还是你先git init/ 切到正确目录?仅在用户明确确认后, 才把当前目录当项目根继续。
检查以下各项是否存在且质量达标。对每项给出状态:
| 状态 | 含义 |
|---|---|
| OK | 存在且质量达标 |
| WEAK | 存在但内容不足或过时 |
| MISSING | 完全缺失 |
| N/A | 不适用于此项目 |
检查清单
# 逐项检查(按优先级排序)
# P0 — 基础必备
[ -f "README.md" ] && echo "README.md: exists" || echo "README.md: MISSING"
[ -f "LICENSE" ] || [ -f "LICENSE.md" ] && echo "LICENSE: exists" || echo "LICENSE: MISSING"
[ -f ".gitignore" ] && echo ".gitignore: exists" || echo ".gitignore: MISSING"
# P1 — 协作规范
[ -f "CONTRIBUTING.md" ] && echo "CONTRIBUTING.md: exists" || echo "CONTRIBUTING.md: MISSING"
[ -f "CODE_OF_CONDUCT.md" ] && echo "CODE_OF_CONDUCT.md: exists" || echo "CODE_OF_CONDUCT.md: MISSING"
[ -f "CHANGELOG.md" ] && echo "CHANGELOG.md: exists" || echo "CHANGELOG.md: MISSING"
# P2 — GitHub 配置
[ -d ".github/ISSUE_TEMPLATE" ] && echo "Issue templates: exists" || echo "Issue templates: MISSING"
[ -f ".github/pull_request_template.md" ] && echo "PR template: exists" || echo "PR template: MISSING"
[ -d ".github/workflows" ] && echo "GitHub Actions: exists" || echo "GitHub Actions: MISSING"
# P3 — 项目元数据
# README badges(在 README 中检查 shields.io 或类似徽章)
# package.json 的 description/keywords/repository 字段
# GitHub repo 的 description 和 topics
What ships with it
10 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.
- 12d ago First seen · 277 lines · 207 tokens per session scan A 6f11f1fe7c95
github-repo-completeness is a skill published in the GitHub repository tranfu-labs/tranfu-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 207 tokens to every session and 4,551 once invoked, about $0.0010 per session on Opus 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…