Borrowing it
Nothing to install: this file belongs to KevinRabun/judges. 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/KevinRabun/judges/main/.github/instructions/release.instructions.mdgit clone --depth 1 https://github.com/KevinRabun/judgesWrote 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/kevinrabun/judges/release)<a href="https://agentmods.dev/instructions/kevinrabun/judges/release"><img src="https://agentmods.dev/badge/instructions/kevinrabun/judges/release/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/kevinrabun/judges/release"><img src="https://agentmods.dev/badge/instructions/kevinrabun/judges/release.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.01657 | $0.01657 |
| Opus 5.5 | $0.00663 | $0.00663 |
| Sonnet 5.5 | $0.00331 | $0.00331 |
| Haiku 4.5 | $0.00166 | $0.00166 |
Grade A, and why
judges release.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 1mo 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release & Deployment — Agent Instructions
When preparing and publishing a new release of @kevinrabun/judges, follow this checklist exactly. The publish workflow is automated via GitHub Actions — your job is to prepare the commit and tag.
Overview
Publishing is triggered by pushing a v* git tag (e.g., v3.18.1). The publish-mcp.yml workflow handles:
- npm publish — builds, packs, and publishes
@kevinrabun/judgesto the npm registry with provenance - npm publish (CLI) — publishes
@kevinrabun/judges-clito the npm registry with provenance (version synced automatically) - GitHub Release — creates a release from the tag with auto-generated notes
- MCP Registry — publishes
server.jsonto the Model Context Protocol registry viamcp-publisher - VS Code Marketplace — syncs the extension version from the git tag, installs the local tarball, and publishes via
vsce
You do not need to run npm publish or vsce publish locally — the action does it all. Your responsibility is: version bumps, changelogs, commit, and tag.
Files That Need Version Updates
Update the version string in all four of these files:
| File | Field(s) | Example |
|---|---|---|
package.json |
"version" |
"version": "3.18.1" |
server.json |
"version" (top-level) and "packages[0].version" |
Both must match |
vscode-extension/package.json |
"version" |
"version": "3.18.1" |
server.jsonhas two version fields — the top-level"version"and"packages[0].version". Both must be updated. This file has historically gone stale; always verify it.
action.ymldoes not contain a version string — it is referenced by tag (e.g.,uses: KevinRabun/[email protected]), so no edit is needed.
The CI workflow patches
vscode-extension/package.jsonat publish time from the git tag, but keep it in sync locally to avoid confusion.
Changelogs That Need Updating
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.
- 1mo ago First seen · 173 lines · 1,657 tokens per session scan A 3f926576898f
judges release.instructions.md is an instructions file published in the GitHub repository KevinRabun/judges (7 stars, last pushed 4mo ago), licensed MIT. It adds 1,657 tokens to every session, about $0.0066 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-31.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.