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 agentmods add skills/sidiangongyuan/codex-skills-library/github-project-releasenpx skills add sidiangongyuan/codex-skills-library --skill github-project-releasegit clone --depth 1 https://github.com/sidiangongyuan/codex-skills-libraryWrote 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/sidiangongyuan/codex-skills-library/github-project-release)<a href="https://agentmods.dev/skills/sidiangongyuan/codex-skills-library/github-project-release"><img src="https://agentmods.dev/badge/skills/sidiangongyuan/codex-skills-library/github-project-release.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.00950 |
| Opus 5 | $0.00026 | $0.00475 |
| Sonnet 5 | $0.00010 | $0.00190 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
github-project-release 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 5d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Project Release
Turn a local project into a clean GitHub repository that is safe to make public later. Default to research-code release behavior: clean copy first, private GitHub repo first, audit before push.
Workflow
-
Inspect the source project before copying.
- Identify the runnable entrypoints, key configs, curated figures/tables, license, citation files, and upstream dependencies.
- Treat the codebase as source of truth. Do not preserve stale upstream README language as the release front page.
-
Check credentials.
- Run
scripts/github_project_release.py auth-check. - Use the active
ghaccount as the default owner. - Never ask the user to paste a GitHub token into chat. If auth is missing, ask them to run
gh auth loginor provide credentials through a secure non-chat channel.
- Run
-
Prepare a clean release copy.
- Run
scripts/github_project_release.py prepare --source <project> --dest <release-dir>. - Keep only what a new user needs to understand and run the project.
- Exclude datasets, checkpoints, logs, generated outputs, raw experiment dumps, paper PDFs, local submission material, and exploratory files unless the user explicitly overrides the default.
- Run
-
Write or rewrite the README.
- Read
references/readme_playbook.mdbefore drafting README content. - Use English by default.
- Write for external readers, not for the project owner.
- For research code, cover Context + Run + Cite: what it is, what problem it solves, what is included, how to install/run the minimal path, and how to cite current and upstream work.
- Read
-
Audit before publishing.
- Run
scripts/github_project_release.py audit --path <release-dir>. - Treat reported high-risk items as blockers unless the user explicitly accepts them.
- If a paper link is not public, use
Paper link: coming soon.and do not upload PDFs.
- Run
-
Publish privately.
- Run
scripts/github_project_release.py publish --release-dir <release-dir>. - If the repo does not exist, create a private repo.
- If it exists, push only safe non-rewriting updates.
- Do not force-push, delete, overwrite, or make the repo public unless explicitly requested.
- Run
What ships with it
4 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.
- 5d ago First seen · 95 lines · 52 tokens per session scan A 52cc9d2d5fa5
github-project-release is a skill published in the GitHub repository sidiangongyuan/codex-skills-library (8 stars, last pushed 13d ago), licensed MIT. It adds 52 tokens to every session and 950 once invoked, about $0.0003 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-skills
Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, GitHub Releases, annotated tags, historical release backfill, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送", "release notes", "GitHub Release"…
git-workflow
Git 工作流专家。规范化版本控制，确保提交历史清晰可追溯。支持 Conventional Commits 规范、Pull Request 最佳实践、分支管理策略和自动化工作流。.
git-publish-release
当用户明确要求"发布项目到 GitHub"、"创建 GitHub Release"或"生成 Release Notes"时使用。智能分析 tag 间历史变化并生成专业的 Release Notes；明确发布/创建请求时自动创建 GitHub Release，单独的 notes/历史总结请求仅生成预览，除非用户随后确认发布。支持首次发布、常规版本、预发布版本（alpha/beta/rc），自动识别 prerelease 标记。.
release-gate-loop
发版前自动验证闸门——V 验证 + F 修复循环（verdict FAIL → F 改代码 → 跑 audit → V 重验），最大 3 轮直到 PASS。纯只读验证 + 最小修复。.
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
mini-program-release-skill
Govern mini-program release readiness and evidence across source branches, semantic versions, build artifacts, test flags, debug paths, sensitive data, permissions, privacy declarations, platform uploads, review submissions, staged versions, production releases, and rollback plans. Use when users ask for a release…