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-build/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-build)<a href="https://agentmods.dev/skills/coding-by-feng/ai-agent-session-center/electron-build"><img src="https://agentmods.dev/badge/skills/coding-by-feng/ai-agent-session-center/electron-build/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/coding-by-feng/ai-agent-session-center/electron-build"><img src="https://agentmods.dev/badge/skills/coding-by-feng/ai-agent-session-center/electron-build.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.00048 | $0.00359 |
| Opus 5 | $0.00024 | $0.00179 |
| Sonnet 5 | $0.00010 | $0.00072 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
electron-build 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 9d 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
Build Electron Distributables
Build the Electron app from the repository root and verify the versioned macOS artifacts. Do not commit, push, tag, or publish as part of this skill.
Workflow
- Resolve the Git root and read the applicable
AGENTS.mdandCLAUDE.md. - Inspect
git status --shortand preserve every unrelated local change. - Confirm
package.jsondefineselectron:buildand read its current version. - Run
npm run electron:buildand stream the output. - If the build fails, diagnose the first actionable error. Apply only a narrow, in-scope fix that does not overwrite existing work, then rerun the smallest relevant check before retrying the build. Report the blocker instead when a safe fix needs user direction, credentials, signing access, or a broader behavior change.
- Verify that these non-empty artifacts exist for the package version:
dist/AI Agent Session Center-<version>-arm64.dmgdist/AI Agent Session Center-<version>-arm64-mac.zip
- Report success or failure, artifact paths and sizes, and any source changes made while resolving a build failure. Include SHA-256 checksums when the artifacts may be handed off or uploaded.
Do not treat an exit code of zero as sufficient if either expected artifact is missing or empty.
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.
- 9d ago First seen · 32 lines · 48 tokens per session scan A 42daf76337e8
electron-build is a skill published in the GitHub repository coding-by-feng/ai-agent-session-center (82 stars, last pushed 12d ago), licensed MIT. It adds 48 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-30.
Other skills, from other repositories
vibe-research
Deep research and market validation for app ideas. Use when starting a new project, validating an idea, or when the user says "research my idea", "validate my app", or "help me start a new project".
pre-landing-review
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when explicitly asked for the specialized pre-landing workflow. Product /review requests are handled by OpenBitFun's unified Review mechanism instead.…
miniapp-dev
A development guide for BitFun MiniApps, which are small applications that run inside BitFun. It covers creating new MiniApps as well as maintaining the MiniApp framework.
investigate
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug…
wechat-article-writer
A Chinese-language content-creation workflow for public-account and social-media writing. It supports article drafting, cover images, illustrations, process diagrams, style analysis, and adapting writing to selected styles.
pr-review-canvas
Create a OpenBitFun Canvas for reviewing a pull request, branch diff, or change set with Cursor-style diff cards, review maps, risk callouts, and focused reviewer flow. Use when the user asks for a PR review canvas, diff walkthrough, change-set overview, or visual review summary.