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/kyungseo/skillstead/github-release-guidenpx skills add kyungseo/skillstead --skill github-release-guidegit clone --depth 1 https://github.com/kyungseo/skillsteadWhat 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.00113 | $0.01919 |
| Opus 5 | $0.00056 | $0.00959 |
| Sonnet 5 | $0.00023 | $0.00384 |
| Haiku 4.5 | $0.00011 | $0.00192 |
Grade A, and why
github-release-guide 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 2d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
github-release-guide
Guide a GitHub release without taking release authority away from the user. Keep unknowns visible, fail closed on release-critical blockers, preview every material mutation, and verify the public result.
Package map
Load references progressively, but never skip a required load:
| File | Load rule |
|---|---|
references/assessment.md |
Always load before classifying readiness or proposing a mutation |
references/first-public.md |
Load for an existing private github.com repository's first public release |
references/version-release.md |
Load for every new version released from an already-public github.com repository |
If a selected profile reference cannot be loaded, continue only with a partial read-only Assess and mark the missing profile rules as unknown. Do not propose or execute Guided actions until the full selected profile reference is loaded.
Supported contract
Support only:
- Mode:
AssessorGuided - Release profile:
first-publicorversion-release - Provider:
github.com - Claim-audit profile:
public-baselineby default, orinternal-strictonly when the user or a repository policy explicitly selects it
Never infer internal-strict from a repository name, owner, visibility, organization, or local path.
Never treat the current working directory as the release target without confirming repository identity.
If the user asks for an unsupported release type, stop at a read-only boundary assessment and explain the missing adapter or specialist handoff. Do not stretch this contract to cover it.
Establish the target
Before classifying readiness, confirm or discover without mutation:
- GitHub owner and repository name, canonical URL, and local root if one exists.
- Current visibility and default branch.
- Requested mode and release profile.
- Release authority: who may approve file, Git, visibility, settings, and GitHub Release mutations.
- Documentation language and release-communication language.
- Claim-audit profile and any explicit repository release policy.
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.
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.
- 2d ago First seen · 184 lines · 113 tokens per session scan A 332665130d3d
github-release-guide is a skill published in the GitHub repository kyungseo/skillstead (78 stars, last pushed 2d ago), licensed Apache-2.0. It adds 113 tokens to every session and 1,919 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-30.
Other skills, from other repositories
data-viz-renderer
Generate self-contained HTML/SVG infographics from JSON data, including stat cards, bar charts, flow diagrams, and mixed dashboards. Offers 8 color palettes and built-in icons with no external dependencies. Triggered when users request data visualization, infographics, charts, or dashboards.
dsh-plugin-publisher
Publish a validated DSH plugin package (@deepseek-ai/dsh- or @lovstudio/dsh-) to npm, git, or tarball channels and verify it loads in the DeepSeek Harness. Use when the user asks to publish, release, or ship a plugin. 触发：发布插件 / 上架插件 / release dsh 插件。.
release-finalizer
Merges a release PR, associates it with resolved issues, replies to issue reporters, and closes issues. Use after PR review is complete and ready for merge. Closes the release cycle.
release-prep
Orchestrates the full release preparation flow for a plugin — version sync across 7+ files, bilingual release notes creation, and commit message drafting. Use before submitting a PR. Does NOT push or create a PR; that is handled by pr-submitter.
publish-no-version-bump
Commit and push code to GitHub, then publish to OpenWebUI official marketplace without updating version. Use when fixing bugs or optimizing performance that doesn't warrant a version bump.
version-bumper
Automates version upgrades and changelog synchronization across 7+ files (Code, READMEs, Docs). Use when a plugin is ready for release to ensure version consistency.