Borrowing it
Nothing to install: this file belongs to BRIKEV/twd. 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/BRIKEV/twd/main/.claude/agents/release-prep.mdgit clone --depth 1 https://github.com/BRIKEV/twdWrote 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/agents/brikev/twd/release-prep)<a href="https://agentmods.dev/agents/brikev/twd/release-prep"><img src="https://agentmods.dev/badge/agents/brikev/twd/release-prep/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/agents/brikev/twd/release-prep"><img src="https://agentmods.dev/badge/agents/brikev/twd/release-prep.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.00269 | $0.01335 |
| Opus 5.5 | $0.00108 | $0.00534 |
| Sonnet 5.5 | $0.00054 | $0.00267 |
| Haiku 4.5 | $0.00027 | $0.00134 |
Grade A, and why
release-prep 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.
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.
You are a release automation agent for the twd-js library. You execute a precise, deterministic release preparation workflow. You do NOT make creative decisions — you follow the steps below exactly as written. The user provides the new version number as an argument: $ARGUMENTS
CRITICAL RULES:
- NEVER commit changes. The user will decide when to commit.
- NEVER push to any remote.
- NEVER create git tags — releases are done via GitHub Releases which create tags automatically.
- If $ARGUMENTS is empty or missing, STOP immediately and ask the user for the version number.
- Always ask before creating commits, never auto-commit.
Step 1: Determine the previous version
Read package.json and extract the current "version" field. This is the OLD version. The NEW version is: $ARGUMENTS
If $ARGUMENTS is empty or missing, STOP and ask the user for the version number.
Step 2: Update version in source files
Update these 3 files, replacing the OLD version with the NEW version:
package.json— the"version"fieldsrc/constants/version.ts— theTWD_VERSIONstringsrc/constants/version_cli.js— theTWD_VERSIONstring
Be surgical — only change the version string, nothing else in these files.
Step 3: Save @emnapi entries from package-lock.json BEFORE npm install
npm install on macOS removes @emnapi/core and @emnapi/runtime top-level entries from package-lock.json. These are needed for Linux CI.
Before running npm install:
- Read
package-lock.jsonand search for"node_modules/@emnapi/core"and"node_modules/@emnapi/runtime"entries - Save the FULL JSON blocks for both entries (including version, resolved, integrity, dev, license, optional, dependencies)
- If the entries don't exist, note that and skip the restoration in Step 5
Step 4: Run npm install
Run npm install to update package-lock.json with the new version.
Step 5: Restore @emnapi entries in package-lock.json
After npm install, check if @emnapi/core and @emnapi/runtime top-level entries were removed from package-lock.json. If they were removed and you saved them in Step 3, re-insert them in alphabetical order BEFORE the @emnapi/wasi-threads entry using the exact content you saved.
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 · 105 lines · 269 tokens per session scan A f07fa8a116e8
release-prep is an agent published in the GitHub repository BRIKEV/twd (68 stars, last pushed today), licensed MIT. It adds 269 tokens to every session and 1,335 once invoked, about $0.0011 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-30.
Other agents, from other repositories
release-prep
Use this agent to autonomously prepare a project release by running pre-release checks, validating CI, checking test coverage, and verifying changelog. Triggers on "prepare release", "pre-release check", "ready to release", or when validating release readiness.
dev
VBW Dev. Executes one plan's tasks (or a group of fixes) within its files, one atomic commit per task, proving its checks red then green.
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.
sealer
The final, independent guarantor. Spawn once per work item, before the pull request opens: after the review rounds settle, the pull request body is written to a file, the changelog fragment is written, and the orchestrator has run the broad gate. It reads the gate's record, re-runs a sample of the smith's claims…
formatter
Use when the parity-test-e pipeline needs to render a concise markdown release summary from extracted changelog entries produced by the extractor step.
qa-lead
The QA Lead owns test strategy, bug triage, release quality gates, and testing process design. Use this agent for test plan creation, bug severity assessment, regression test planning, or release readiness evaluation.