Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/znlgis/my-opencode-deepseek-confignpx agentmods add skills/znlgis/my-opencode-deepseek-config/git-releaseWrote 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/znlgis/my-opencode-deepseek-config/git-release)<a href="https://agentmods.dev/skills/znlgis/my-opencode-deepseek-config/git-release"><img src="https://agentmods.dev/badge/skills/znlgis/my-opencode-deepseek-config/git-release/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/znlgis/my-opencode-deepseek-config/git-release"><img src="https://agentmods.dev/badge/skills/znlgis/my-opencode-deepseek-config/git-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.01068 |
| Opus 5.5 | $0.00025 | $0.00427 |
| Sonnet 5.5 | $0.00013 | $0.00214 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
git-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 1mo 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Release
Turn a set of merged changes into a clean, tagged release: collect what
changed, pick the right version, and produce the exact commands to cut it.
Pairs well with the gh-cli skill.
What I do
- Draft release notes from the commits/PRs since the last tag.
- Recommend a SemVer bump (major / minor / patch) from the change types.
- Provide copy-pasteable
git tagandgh release createcommands.
When to use me
Use this when you are preparing a tagged release, drafting a changelog, or the user asks to "cut a release", "bump the version", or "publish a new version".
Step 1: Establish the baseline
git fetch --tags --force
git describe --tags --abbrev=0 # most recent tag, e.g. v1.3.0
git log <last-tag>..HEAD --oneline # commits since that tag
If there is no prior tag, use the repository's first commit as the baseline
(git log --oneline) and start at v0.1.0 (or v1.0.0 for a first stable
release).
Step 2: Decide the version (SemVer)
Inspect the Conventional Commit types since the last tag and pick the highest applicable bump:
| Found in the range | Bump |
|---|---|
any BREAKING CHANGE / ! marker |
major |
any feat: |
minor |
only fix: / perf: / refactor: / docs: / ... |
patch |
MAJOR.MINOR.PATCH — incrementing major resets minor and patch to 0;
incrementing minor resets patch to 0. Pre-1.0 projects may treat feat as
patch and BREAKING CHANGE as minor — match the project's existing cadence.
Step 3: Draft the release notes
Group changes by type, newest first, and link PRs/issues:
## v1.4.0 — 2026-01-15
### Features
- add OAuth2 device-code login (#123)
### Fixes
- guard against null user before serializing (#130)
### Docs
- clarify skill auto-discovery paths (#128)
Prefer letting GitHub generate a first draft, then edit it:
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.
- 1mo ago First seen · 126 lines · 63 tokens per session scan A c42fea1d6376
git-release is a skill published in the GitHub repository znlgis/my-opencode-deepseek-config (59 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,068 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
release
Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASERULE.md, then guides the release.
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
release
Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.
prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…