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/dvnghiem/flowdeck/git-releasenpx skills add DVNghiem/FlowDeck --skill git-releasegit clone --depth 1 https://github.com/DVNghiem/FlowDeckWhat 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.00035 | $0.00680 |
| Opus 5 | $0.00017 | $0.00340 |
| Sonnet 5 | $0.00007 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
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 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Release Skill
Creates releases with consistent versioning, accurate changelogs, and proper tagging.
When to Activate
Activate when:
- A release is complete and ready to ship
- You need to cut a release tag
- You need to generate a CHANGELOG entry
Core Principles
- Semver strictly: major.minor.patch
- Conventional commits drive the version bump automatically
- Changelog is for humans: group by type, use plain language
- One release per tag — no force-pushing tags
Workflow
- Collect commits —
git log [last-tag]..HEAD --oneline - Determine version bump from commits:
- Breaking change (
!orBREAKING CHANGE:) → major bump feat:→ minor bumpfix:,refactor:,perf:→ patch bumpdocs:,test:,chore:→ no version bump (unless last release)
- Breaking change (
- Draft changelog — group commits by type
- Update CHANGELOG.md — prepend new version under
## Unreleased - Tag and push — provide the exact commands
Conventional Commits Types
| Type | Version Bump | Description |
|---|---|---|
feat |
minor | New feature |
fix |
patch | Bug fix |
perf |
patch | Performance improvement |
refactor |
patch | Code change, no behavior change |
docs |
none | Documentation only |
test |
none | Adding or updating tests |
chore |
none | Maintenance, dependencies |
ci |
none | CI/CD configuration |
feat! or BREAKING CHANGE: |
major | Breaking API change |
Changelog Format
Follow Keep a Changelog (keepachangelog.com):
## [1.2.0] — 2024-01-15
### Added
- User authentication via JWT (feat: add JWT auth)
- Password reset via email (feat: add password reset)
### Fixed
- Token expiry calculation was off by one day (fix: correct token expiry)
### Changed
- Migrated from bcrypt to argon2 for better security (refactor: use argon2)
Release Commands
# After updating CHANGELOG.md
git add CHANGELOG.md
git commit -m "chore(release): v1.2.0"
git tag -a v1.2.0 -m "Release v1.2.0"
git push origin main --tags
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 · 95 lines · 35 tokens per session scan A b659b2697379
git-release is a skill published in the GitHub repository DVNghiem/FlowDeck (24 stars, last pushed 13d ago), licensed MIT. It adds 35 tokens to every session and 680 once invoked, about $0.0002 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
oh-my-opencode-slim
Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos…
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
deepwork
High-cost orchestrator workflow for large, high-risk, multi-phase coding efforts with meaningful dependencies and review gates. Do not activate for routine multi-file changes.
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.