What is devops-pipeline?

A build and release guide for the Prime-Silo desktop app, an Electron application that combines a Node server, browser interface, and Benny runtime.

Building shell-only tests, creating local builds, packaging Windows, macOS, or Linux releases, updating the version, and debugging release CI, including Open-Studio services and the Benny runtime.

It gives developers the commands and choices needed to test, package, version, sign, and release the app without guessing how its parts are bundled.

How binary16labs/prime-silo configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to binary16labs/prime-silo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/binary16labs/prime-silo/main/.claude/skills/devops-pipeline/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/binary16labs/prime-silo

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/binary16labs/prime-silo/devops-pipeline/github.svg)](https://agentmods.dev/skills/binary16labs/prime-silo/devops-pipeline)

Your own site

<a href="https://agentmods.dev/skills/binary16labs/prime-silo/devops-pipeline"><img src="https://agentmods.dev/badge/skills/binary16labs/prime-silo/devops-pipeline/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/binary16labs/prime-silo/devops-pipeline"><img src="https://agentmods.dev/badge/skills/binary16labs/prime-silo/devops-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,673 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00075	$0.01673
Opus 5.5	$0.00030	$0.00669
Sonnet 5.5	$0.00015	$0.00335
Haiku 4.5	$0.00007	$0.00167

Measured 2mo ago against content hash 00cb68b78a2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

devops-pipeline 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 2mo 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.

.claude/skills/devops-pipeline/SKILL.md · 121 lines

How it starts

The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Prime-Silo DevOps pipeline

Prime-Silo packages as an Electron desktop app ("Space Agent") via electron-builder. Two product layers ship together: the Space-Agent shell (Node server + browser UI, run in-process) and the Benny runtime (Python + Neo4j + JRE) which is either bundled (zero-install) or driven from an external $BENNY_HOME.

All commands run from the repo root: C:\Users\nsdha\OneDrive\binary16\prime-silo.

0. One-time: install packaging deps

electron + electron-builder live under packaging/. If packaging/node_modules is missing, run first:

npm run install:packaging

1. Build types (pick the lightest that proves what you need)

Goal	Command	Output	Notes
Fast shell-only test (validates main/tray/pet/UI changes)	`npm run desktop:pack`	`dist/desktop/windows/win-unpacked/Space Agent.exe`	No runtime bundle. Quick. Best for verifying desktop/main-process changes.
Zero-install local test (shell app)	`npm run desktop:localtest`	`dist/desktop/windows/win-unpacked/Space Agent.exe`	Builds + signs the shell app only. NOTE: it sets `PRIME_SILO_BUNDLE_RUNTIME=1` but that env var is read nowhere since v1.2.9 — the runtime bundle was decoupled from the installer, so this does NOT assemble Python/Neo4j/JRE or run pip. Use the row below for the runtime bundle.
Runtime bundle (the docling/torch/Neo4j artifact)	`node packaging/scripts/pack-runtime-bundle.js`	`dist/runtime-bundle/runtime-bundle-<plat>-<arch>.tar.gz` (+ `.sha256`, `.json`)	Assembles embedded Python + `site/` (full pip tree incl. docling/torch — slow, multi-GB) + Neo4j + JRE, tars the release asset the app fetches on first launch. THIS is what to validate after changing `BUNDLE_RUNTIME_REQUIREMENTS`. ~909 MB (2026-06).
Windows installer	`npm run package:desktop:windows`	NSIS installer in `dist/`	Full build.
All Windows arches	`npm run package:desktop:windows:all`	x64 + arm64
macOS / Linux	`npm run package:desktop:{macos,linux}[:all]`	dmg+zip / AppImage	Run on the target OS.

Read the full file on GitHub · 121 lines

Changes

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.

2mo ago First seen · 121 lines · 75 tokens per session scan A 00cb68b78a2f

Subscribe to this mod's changes

devops-pipeline is a skill published in the GitHub repository binary16labs/prime-silo (5 stars, last pushed 13d ago), licensed MIT. It adds 75 tokens to every session and 1,673 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-31.

DevOps and cloud Git and workflow Releases a2a agent-harness agent-os agent-to-agent binary16 local-first

devops-pipeline next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
devops-pipelinebinary16labs/prime-silo	Skill	5	13d ago	MIT	A	75	Claude Code
git-cliffmoabualruz/fulcrum	Skill	7	1mo ago	MIT	A	47	Claude Code
ghmoabualruz/fulcrum	Skill	7	1mo ago	MIT	A	48	Claude Code
validate-release-greendiegosouzapw/OmniRoute	Skill	83k	5d ago	MIT	A	47	Claude Code, Codex
oma-dev-workflowfirst-fluke/oh-my-agent	Skill	1.4k	yesterday	MIT	A	29	Claude Code
publish-siteandrooAGI/starnet	Skill	1.7k	6d ago	MIT	A	50	Claude Code, Codex
publish-harnessruvnet/metaharness	Skill	738	yesterday	MIT	A	37	Claude Code

prime-silo: Skill for Claude Code