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/emlog/skill-lake/release-skillnpx skills add emlog/skill-lake --skill release-skillgit clone --depth 1 https://github.com/emlog/skill-lakeWrote 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/emlog/skill-lake/release-skill)<a href="https://agentmods.dev/skills/emlog/skill-lake/release-skill"><img src="https://agentmods.dev/badge/skills/emlog/skill-lake/release-skill.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.00031 | $0.00359 |
| Opus 5 | $0.00015 | $0.00179 |
| Sonnet 5 | $0.00006 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
app-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 3d 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.
What it actually says
app-release
Use this skill when you need to publish a new version of the Skill Lake application.
Workflow
- Check Prerequisites: Ensure you are on the
mainbranch and have no uncommitted changes. - Determine Version: Ask the user for the new version number (e.g.,
1.1.8) if not provided. - Execute Release: Run the
./release.shscript with the new version as an argument. - Verification: Confirm that the build succeeded, the DMG was created, and the release was pushed to GitHub and the Homebrew tap.
Usage
./release.sh <new_version>
Example:
./release.sh 1.1.8
Features
- Code Validation: Automatically runs
flutter analyzeand checks formatting before building. - Automated Build: Builds the macOS app in release mode.
- DMG Packaging: Creates a signed DMG package for easy installation.
- Git Automation: Handles version bumping in
pubspec.yaml, commits, tagging, and pushing. - GitHub Integration: Creates or updates a GitHub Release and uploads the DMG.
- Homebrew Sync: Automatically updates the Homebrew Cask in the dedicated tap repository.
- UI Sync: Ensures the version displayed in the "About" dialog matches the released version using
package_info_plus.
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.
- 3d ago First seen · 37 lines · 31 tokens per session scan A 8df4bd71a2f1
app-release is a skill published in the GitHub repository emlog/skill-lake (2 stars, last pushed 18d ago), licensed MIT. It adds 31 tokens to every session and 359 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-31.
Other skills, from other repositories
github-release-notes-writer
Draft or update user-focused GitHub Release Notes from verified tags, commits, pull requests, existing releases, and supplied changelog baselines. Use when preparing prerelease or stable release notes, turning GitHub's generated What's Changed list into a curated narrative, documenting upgrades or breaking changes, or…
github-release-pr-writer
Draft or update GitHub release pull request descriptions from verified tags, commits, merged pull requests, and the release diff. Use when a PR prepares a version, aligns release metadata, promotes a prerelease, or needs a reviewer-focused release summary, exact change inventory, breaking-change section, or migration…
glab-cli
GitLab CLI (glab) reference and workflow for repository, merge request, issue, CI/CD, release, and API operations across GitLab.com and self-managed or dedicated instances. Use when Codex needs to run or explain glab commands, usually by relying on the current glab context first, and only falling back to git remote -v…
otel-changelog-pr-verifier
Verify whether CHANGELOG entries in an OpenTelemetry Go repository point to the correct pull requests and whether each (#NNNN) matches the described change. Use when checking a release PR, validating a CHANGELOG section, or screening only mismatched changelog-to-PR references.
bump-version
Automate version bumping following semantic versioning and changelog management. Use when the user wants to bump a version, create a release, update the changelog, or tag a new version in a project using semver conventions and Keep a Changelog format.
anysearch
Real-time search engine supporting web search, vertical domain search, parallel batch search, and URL content extraction.