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-delivery-checkgit 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-delivery-check)<a href="https://agentmods.dev/skills/tranfu-labs/tranfu-skills/github-delivery-check"><img src="https://agentmods.dev/badge/skills/tranfu-labs/tranfu-skills/github-delivery-check/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-delivery-check"><img src="https://agentmods.dev/badge/skills/tranfu-labs/tranfu-skills/github-delivery-check.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.00127 | $0.03404 |
| Opus 5 | $0.00063 | $0.01702 |
| Sonnet 5 | $0.00025 | $0.00681 |
| Haiku 4.5 | $0.00013 | $0.00340 |
Grade A, and why
github-delivery-check 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 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.
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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Delivery Check
Target type: product project repository with code, README, config examples, and deployment files. Do not use this skill for prompts, other skills, agent definitions, docs-only assets, or product copy alone.
Prepare a product project for GitHub delivery so another teammate can understand, configure, deploy, and verify it.
Default action: inspect the project, fix delivery docs, verify locally, and push directly to the GitHub main branch. MUST stop only when GitHub authorization is missing, real secret risk exists, required product facts are missing, required verification fails, Git state is unsafe, or the user requested discussion-only mode.
When To Use
Use this skill when the user wants to:
- push a product project to GitHub
- create a new GitHub repository
- update an existing GitHub repository
- make a project deployable from README
- hand deployment configuration to engineers
Also match Chinese requests:
- "推到 GitHub"
- "创建 GitHub 仓库"
- "这个产品首次提交"
- "整理成可部署项目"
- "用 GitHub交付规范 Skill"
Do NOT use this skill when:
- the user only wants ordinary code changes -> use normal coding workflow
- the user asks for code review -> use review workflow
- the user asks to deploy production without GitHub delivery -> use deploy workflow
- the user explicitly says discussion-only or planning-only -> discuss only and do not push
If intent is ambiguous, ask one confirmation question before doing delivery work:
Do you want me to push this project to GitHub main, update an existing repository, or only prepare/check the README without pushing?
Non-Negotiables
- MUST inspect the actual project files before asking the user to classify the project.
- MUST verify locally with real commands when the project has runnable commands.
- MUST complete README deployment instructions before pushing.
- MUST push to main by default when delivery is safe and authorized.
- NEVER say GitHub push means production is deployed.
- NEVER say local build success means production is live.
- NEVER invent GitHub authorization codes, repository URLs, or production URLs.
- NEVER commit
.env, private keys, database files, dependency directories, build caches, or local-only config with real values.
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.
- 10d ago First seen · 390 lines · 127 tokens per session scan A 81ebbe0a1836
github-delivery-check is a skill published in the GitHub repository tranfu-labs/tranfu-skills (2 stars, last pushed today), licensed MIT. It adds 127 tokens to every session and 3,404 once invoked, about $0.0006 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.