Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/binary16labs/prime-silonpx agentmods add skills/binary16labs/prime-silo/prime-silo-devopsWrote 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/binary16labs/prime-silo/prime-silo-devops)<a href="https://agentmods.dev/skills/binary16labs/prime-silo/prime-silo-devops"><img src="https://agentmods.dev/badge/skills/binary16labs/prime-silo/prime-silo-devops/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/binary16labs/prime-silo/prime-silo-devops"><img src="https://agentmods.dev/badge/skills/binary16labs/prime-silo/prime-silo-devops.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00046 | $0.00812 |
| Opus 5.5 | $0.00018 | $0.00325 |
| Sonnet 5.5 | $0.00009 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
prime-silo-devops 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 1mo 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prime-Silo DevOps & Release Management
Use this skill whenever you are tasked with managing the SDLC, triggering a new release, checking CI/CD workflows, or troubleshooting build pipelines for the prime-silo project.
1. Prerequisites for Releasing
Before creating a release, you MUST verify:
- All changes are committed and merged into the
mainbranch. - The working directory is completely clean (
git statusshows no uncommitted changes). - All relevant documentation is updated.
2. Creating a Release (Tagging)
DO NOT use manual git tag or manually edit package.json to bump the version. You must use the managed release script.
To create a release:
# On Windows PowerShell
.\scripts\manage-release.ps1 <patch|minor|major>
# On macOS/Linux Bash
node scripts/manage-release.js <patch|minor|major>
This script will automatically read the current version, bump it appropriately, update package.json, create a commit named "Release: X.Y.Z", and create an annotated git tag.
3. Pushing the Release
CRITICAL PUSH ORDER: You MUST push the release commit to main before pushing the tag. If you push the tag first, the release gate will skip the build jobs because the tag's commit isn't on origin/main yet!
# Step 1: Push the commit FIRST
git push origin main
# Step 2: Push the tag SECOND
git push origin vX.Y.Z
4. Monitoring the CI/CD Pipeline
Releases trigger .github/workflows/release-desktop.yml. Snapshot builds run automatically on every push to main via .github/workflows/snapshot-build.yml.
To monitor workflow status:
# Check workflow status
gh run list --workflow=release-desktop.yml --limit 1
# View detailed progress or a specific job
gh run view <run-id>
gh run view <run-id> --job <job-id>
A normal release build takes ~30 minutes to complete the matrix of 6 platforms (Windows x64/arm64, macOS x64/arm64, Linux x64/arm64).
5. Troubleshooting & Rollbacks
If a build job skips unexpectedly, check the release gate:
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.
- 1mo ago First seen · 105 lines · 46 tokens per session scan A c57a56384135
prime-silo-devops is a skill published in the GitHub repository binary16labs/prime-silo (5 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 812 once invoked, about $0.0002 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.
Other skills, from other repositories
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
oma-dev-workflow
Configure development tasks, git hooks, CI/CD, or release automation. Use when creating or fixing a repository development workflow.
git-cliff
Use when the user wants to generate a changelog, create release notes from git history, update CHANGELOG.md before tagging a release, produce a changelog from conventional commits, or summarize commits since the last tag.
gh
Use when the user works with GitHub from the command line - listing or viewing pull requests, creating PRs and issues, reviewing or merging, watching workflow runs, downloading release assets, or hitting the REST/GraphQL API.
repo-bootstrap
Automate full ANAMIZED product repo structure (Server OS parity) including USDC, Stripe, badges, CI, skills, AGENTS.md.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.