Borrowing it
Nothing to install: this file belongs to coding-by-feng/ai-agent-session-center. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/coding-by-feng/ai-agent-session-center/main/.agents/skills/electron-release/SKILL.mdgit clone --depth 1 https://github.com/coding-by-feng/ai-agent-session-centerWrote 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/coding-by-feng/ai-agent-session-center/electron-release)<a href="https://agentmods.dev/skills/coding-by-feng/ai-agent-session-center/electron-release"><img src="https://agentmods.dev/badge/skills/coding-by-feng/ai-agent-session-center/electron-release.svg" alt="Measured on agentmods" 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.00049 | $0.01016 |
| Opus 5 | $0.00024 | $0.00508 |
| Sonnet 5 | $0.00010 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
electron-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 8d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Electron Build
Release the reviewed repository changes as the next patch version. This workflow changes version files, creates a commit, pushes it, and creates a public GitHub release, so keep every step scoped and verifiable.
Safety Rules
- Treat explicit invocation or a direct release request as authorization for this release sequence, not for unrelated local files.
- Inspect the worktree before changing it. Preserve unrelated edits and never
use
git add -Aorgit add .. - Exclude local-only state such as
.codex/audit/, root-level generated bundles, screenshots, caches, credentials, and environment files. - Stop for user direction when a dirty file's inclusion is ambiguous or the current branch, remote, or release target is unexpected.
- Never delete or overwrite a remote release, tag, or pushed commit as automatic error recovery.
1. Preflight
- Resolve the Git root and read the applicable
AGENTS.mdandCLAUDE.md. - Inspect
git status --short, the complete relevant diff, the current branch, its upstream, and the configured GitHub remote. - Classify every changed and untracked file as release content, required version metadata, generated artifact, or unrelated local state. Record the exact paths intended for the commit.
- Verify GitHub CLI authentication with
gh auth status. - Refresh tags from the release remote and query the latest published release
with
gh release list. Do not rely only on potentially stale local tags. - Confirm that the next patch version and its
v<version>tag do not already exist locally or on GitHub.
2. Version
- Read the version from
package.json. - Run
npm version patch --no-git-tag-versionsopackage.jsonand an existingpackage-lock.jsonadvance together. - Verify the top-level versions match and inspect the version-file diff. Do not continue if the command changed dependencies or unrelated metadata.
3. Validate and Build
- Run
npm run typecheck. - Run targeted tests appropriate to the reviewed changes and any additional
checks required by
AGENTS.md. - Run
npm run electron:build. Diagnose failures and apply only narrow fixes that remain inside the approved release scope; rerun affected checks after a fix. - Verify these non-empty artifacts for the new version:
dist/AI Agent Session Center-<version>-arm64.dmgdist/AI Agent Session Center-<version>-arm64-mac.zip
- Compute SHA-256 checksums for both artifacts.
What ships with it
1 file 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.
- 8d ago First seen · 100 lines · 49 tokens per session scan A 145b2be0525b
electron-release is a skill published in the GitHub repository coding-by-feng/ai-agent-session-center (82 stars, last pushed 11d ago), licensed MIT. It adds 49 tokens to every session and 1,016 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
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is…
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.
memstack-development-changelog-generator
Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing.
release-notes-generator
Create release notes that summarize features, fixes, and migration guidance for software releases.
keep-a-changelog-generator
Generate changelog entries from git history using Keep a Changelog structure and user-facing release language.
auto-pr
Use when the user invokes /auto-pr or asks to "open N PRs against ", "auto-contribute to ", or "raise mergeable PRs automatically". Wraps the vouch auto-pr CLI: points at any github repo, learns its contribution norms (from shipped guidance, else synthesized from merged PRs), sources work items (open issues first…