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/v0id-user/setmac/setmac-release-opsnpx skills add v0id-user/setmac --skill setmac-release-opsgit clone --depth 1 https://github.com/v0id-user/setmacWhat 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.00061 | $0.00411 |
| Opus 5 | $0.00030 | $0.00205 |
| Sonnet 5 | $0.00012 | $0.00082 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
setmac-release-ops 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
Setmac Release Ops
Use this skill when
- the user asks to cut
canary,beta, or stable releases - a release workflow or semantic-release config needs changes
- signing, notarization, or Gatekeeper behavior is involved
- the shipped app crashes or behaves differently than
swift run - AI instructions for release work need updating
Core rules
- Use Conventional Commits.
- Keep one logical change per commit.
- Do not hand-edit release version numbers.
- Default to
canaryorbetaunless the user explicitly asks for stable.
Release model
canary->vX.Y.Z-canary.Nbeta->vX.Y.Z-beta.N- stable -> manual
Release Stableworkflow frommain
Required outputs
dist/Setmac.dmgcli/dist/setmac-cli
Validation checklist
Run the smallest relevant set:
uv run semantic-release --noop version
just release-dry-canary
just release-dry-beta
NEW_VERSION="9.99.99-test" bash scripts/release-build.sh
just release-verify
Packaging and signing notes
- Release builds must go through
scripts/release-build.sh. - Packaged apps must include SwiftPM resource bundles from
.build/release/*.bundle. - Shipped resources should load from
Bundle.main. - Ad-hoc signing is acceptable as a fallback, but note that Gatekeeper may still block downloads until Apple notarization secrets are configured.
Reference
Read docs/ai-maintainer-playbook.md for the full release and hotfix workflow.
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 · 56 lines · 61 tokens per session scan A a95859a15d61
setmac-release-ops is a skill published in the GitHub repository v0id-user/setmac (14 stars, last pushed 5mo ago), licensed MIT. It adds 61 tokens to every session and 411 once invoked, about $0.0003 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
npm-release
Guide for setting up automated npm package releases via GitHub Actions using Trusted Publishing (OIDC). Use when creating release workflows, publishing to npm, or troubleshooting CI/CD publish failures.
gitlab-cli
Reference guide for GitLab CLI (glab) commands. Use when running glab commands for issues, merge requests, pipelines, releases, or CI/CD operations, or when the user asks about GitLab CLI syntax.
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
deploy
Use when ready to ship — runs pre-push gates (lint, typecheck, build, tests, security sweep), commits, releases, and pushes. Standalone, never auto-invoked. Push always requires explicit confirmation. Trigger with /hyperflow:deploy, "ship it", "ready to push", "release", "cut a release", "deploy".