Borrowing it
Nothing to install: this file belongs to JBorgia/signaltree. 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/JBorgia/signaltree/main/.github/instructions/release-process.instructions.mdgit clone --depth 1 https://github.com/JBorgia/signaltreeWrote 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/instructions/jborgia/signaltree/release-process)<a href="https://agentmods.dev/instructions/jborgia/signaltree/release-process"><img src="https://agentmods.dev/badge/instructions/jborgia/signaltree/release-process/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/instructions/jborgia/signaltree/release-process"><img src="https://agentmods.dev/badge/instructions/jborgia/signaltree/release-process.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.02922 | $0.02922 |
| Opus 5.5 | $0.01169 | $0.01169 |
| Sonnet 5.5 | $0.00584 | $0.00584 |
| Haiku 4.5 | $0.00292 | $0.00292 |
Grade A, and why
signaltree release-process.instructions.md 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SignalTree Release Process
Critical: DO NOT Skip These Steps
Publishing broken packages to npm damages user trust and creates support burden. This process is mandatory for all releases.
Pre-Release Checklist (Required)
Before running ANY release commands, verify:
1. Working Directory is Clean
git status
# Must show: "nothing to commit, working tree clean"
If there are uncommitted changes, commit or stash them first.
2. You're on the main branch and up-to-date
git checkout main
git pull origin main
3. All dependencies are installed
pnpm install --frozen-lockfile
4. Full validation passes
npm run validate:all
This runs:
- Linting (
lint:all) - Tests (
test:all) - Builds (
build:all) - Type declaration verification (
validate:types) - Package structure checks
- Export validation
If any validation step fails, DO NOT proceed with release.
Release Commands (Use Release Scripts - NOT nx release directly)
SignalTree has comprehensive release automation in scripts/release.sh. ALWAYS use these npm scripts instead of nx release directly.
Recommended Release Flow (Automated)
# For patch releases (bug fixes)
npm run release:patch
# For minor releases (new features, backward compatible)
npm run release:minor
# For major releases (breaking changes)
npm run release:major
What the Release Script Does
The scripts/release.sh script provides a complete, reliable release workflow:
-
Runs comprehensive pre-publish validation (
scripts/pre-publish-validation.sh)- All tests must pass
- All builds must succeed
- Type declarations must be valid
- Bundle sizes verified
- Export integrity checked
-
Bumps versions in all package.json files (workspace + all packages)
-
Updates peer dependencies with correct version constraints
-
Builds all packages in production mode
-
Updates CHANGELOG.md from conventional commits
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 · 439 lines · 2,922 tokens per session scan A 2d3bedcd5059
signaltree release-process.instructions.md is an instructions file published in the GitHub repository JBorgia/signaltree (22 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,922 tokens to every session, about $0.0117 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.