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 agents/brikev/twd/release-prepgit clone --depth 1 https://github.com/BRIKEV/twdWhat 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.00269 | $0.01335 |
| Opus 5 | $0.00134 | $0.00668 |
| Sonnet 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 2d 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.
- 2d ago First seen · 105 lines · 269 tokens per session scan A f07fa8a116e8
release-prep is an agent published in the GitHub repository BRIKEV/twd (58 stars, last pushed 4d ago), licensed MIT. It adds 269 tokens to every session and 1,335 once invoked, about $0.0013 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.