build-release-mindset

build-release-mindset is a skill for Claude Code, Codex from Fergius-Engineering/instincts. It costs 24 tokens per session (463 once invoked), scanned A, original, MIT.

A set of practices for build scripts, releases, packaging, publishing, and continuous integration (automated build and test systems).

In plain words
What is it for?
Use it when changing build or release automation, CI configuration, or package-publishing steps.
Why use it?
It helps prevent unreliable builds, damaged releases, stale files, and changes that cannot be rolled back safely.

Skill for Claude CodeCodex

Part of the instincts plugin — 20 skills, 2 hooks shipped together

Install

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.

agentmods
npx agentmods add skills/fergius-engineering/instincts/build-release-mindset
Any agent
npx skills add Fergius-Engineering/instincts --skill build-release-mindset
Clone the repo
git clone --depth 1 https://github.com/Fergius-Engineering/instincts

Made for: Claude Code, Codex.

Or install instincts, the plugin that ships this one along with the rest of its 20 skills, 2 hooks.

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.

agentmods badge for build-release-mindset

README.md
[![agentmods](https://agentmods.dev/badge/skills/fergius-engineering/instincts/build-release-mindset.svg)](https://agentmods.dev/skills/fergius-engineering/instincts/build-release-mindset)
Your own site
<a href="https://agentmods.dev/skills/fergius-engineering/instincts/build-release-mindset"><img src="https://agentmods.dev/badge/skills/fergius-engineering/instincts/build-release-mindset.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 463 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.00463
Opus 5 $0.00012 $0.00231
Sonnet 5 $0.00005 $0.00093
Haiku 4.5 $0.00002 $0.00046

Measured 4d ago against content hash 4d9b6a06dffe, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

build-release-mindset 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 4d 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.

skills/build-release-mindset/SKILL.md · 35 lines

What it actually says

The rule

Build and release code has a different discipline than feature code: it must be reproducible, abortable, and reversible. A build that depends on whatever the last run left behind is unreliable by definition. Before you change a build step, ask what happens if it crashes halfway, and whether you could undo the release after it ships.

Fires when

Editing a build script, a release or packaging step, a publish flow, or CI config.

How to apply

  • Start from a guaranteed clean state: remove stale artifacts and intermediates, restore any patched config, before you begin.
  • Smoke-test the smallest case first and abort fast if it fails; don't run the full matrix on a setup you haven't proven.
  • Version artifacts into timestamped outputs instead of overwriting, so rollback is trivial.
  • Validate outputs, not just inputs. A silently-empty artifact, or a "0 tests passed" nobody asserted on, is the worst failure mode and the easiest to miss.
  • Protect any global state you patch-and-restore with a lock, so a half-finished run doesn't leave the machine broken.
  • Know the rollback before you ship.

Worked example

A release script builds against eight SDK versions over an hour, then you discover the first one was broken from the start — the whole hour is wasted. A canary fixes it: build the smallest target first, and abort the run if it fails, so a broken setup costs two minutes instead of sixty. The same instinct catches a "0 tests passed" that would otherwise ship green because nobody asserted the count was above zero — a loud failure is always better than a silent bad artifact.

Red flags

Thought Reality
"The machine's probably clean" Probably is not a guarantee; start clean.
"It built, so it's good" Built is not the same as validated. Check the output.
"I'll just overwrite the last build" Then you can't roll back when this one's bad.
"All eight will be fine" Smoke-test one before you spend an hour on eight.
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.

  1. 4d ago First seen · 35 lines · 24 tokens per session scan A 4d9b6a06dffe

Subscribe to this mod's changes

build-release-mindset is a skill published in the GitHub repository Fergius-Engineering/instincts (2 stars, last pushed 9d ago), licensed MIT. It adds 24 tokens to every session and 463 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

pdlc-ship

发布工作流(跑测试 → bump VERSION → 更 CHANGELOG → tag → 触发 CI/CD).

kanfu-panda/pdlc-skills · 28 tokens

deployment-safety

Safe shipping to production on any platform (Render, Vercel, AWS, Docker, bare VM). Use when deploying, releasing, configuring CI/CD, writing Dockerfiles or infra config, running migrations against production, or when the user says "deploy", "release", "go live", "ship", "rollback", or "production".

05-deepak-patidar/claude-skills · 72 tokens

tutti-app-release

Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow. Use for caller workflows, tutti.app.json manifests, @tutti-os/app-release-tools, S3/CloudFront release hosting, latest.json, versions.json, catalog.json, catalog-only…

tutti-os/tutti · 80 tokens

release-bridge

Bridge Server のリリース(バージョンbump + CHANGELOG + タグ → GH Actions で npm publish).

K9i-0/ccpocket · 31 tokens

writing-modpack-changelog

Use when cutting a modpack release. Creates /docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.

hashgraph-online/awesome-codex-plugins · 69 tokens

update-maturin

Bump maturin to the latest release and regenerate .github/workflows/tapo-py.yml, preserving local customizations.

mihai-dinculescu/tapo · 29 tokens