Borrowing it
Nothing to install: this file belongs to s-hiraoku/vscode-sidebar-terminal. 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/s-hiraoku/vscode-sidebar-terminal/main/.claude/commands/prerelease-check.mdgit clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminalWrote 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/commands/s-hiraoku/vscode-sidebar-terminal/prerelease-check)<a href="https://agentmods.dev/commands/s-hiraoku/vscode-sidebar-terminal/prerelease-check"><img src="https://agentmods.dev/badge/commands/s-hiraoku/vscode-sidebar-terminal/prerelease-check/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/commands/s-hiraoku/vscode-sidebar-terminal/prerelease-check"><img src="https://agentmods.dev/badge/commands/s-hiraoku/vscode-sidebar-terminal/prerelease-check.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.00000 | $0.02145 |
| Opus 5 | $0.00000 | $0.01073 |
| Sonnet 5 | $0.00000 | $0.00429 |
| Haiku 4.5 | $0.00000 | $0.00215 |
Grade A, and why
prerelease-check 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 9d 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 — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-release Checklist for VS Code Sidebar Terminal
This document outlines the comprehensive verification steps to be performed before releasing the VS Code Sidebar Terminal extension. The primary focus is to ensure build quality, test coverage, and functional correctness.
Prerequisites
- Node.js >=18.0.0 is installed
- VS Code >=1.74.0 is available for testing
- Project dependencies are installed (
npm install) - Clean git working directory
1. Development Environment Setup
1.1 Initial Setup Verification
# Verify Node.js version
node --version # Should be >= 18.0.0
# Install dependencies
npm install
# Verify TypeScript compilation
npm run compile
Expected: Clean compilation without errors
1.2 Build System Verification
# Test webpack compilation
npm run compile
# Test production build
npm run package
# Verify output files exist
ls -la dist/extension.js dist/webview.js
Expected: Both extension.js and webview.js files are generated successfully
2. Code Quality and Standards
2.1 Lint Checks
# Run ESLint checks
npm run lint
Expected: Zero lint errors (warnings for TypeScript any types are acceptable)
2.2 Code Formatting
# Apply consistent formatting
npm run format
# Verify no files changed after formatting
git status
Expected: No unstaged changes after formatting
2.3 TypeScript Compilation
# Compile tests
npm run compile-tests
# Verify out/ directory structure
ls -la out/test/
Expected: Complete test compilation without TypeScript errors
3. Test Suite Execution
3.1 Unit Tests
# Run core unit tests
npm test
# Run with coverage reporting
npm run test:coverage
Expected:
- Test success rate: ≥93%
- Test coverage: ≥85%
- Total tests: ≥275
3.2 Integration Tests
# Run integration test suite
npm run test:integration
Expected: All integration scenarios pass
3.3 Performance Tests
# Run performance test suite
npm run test:performance
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.
- 9d ago First seen · 381 lines · 0 tokens per session scan A 6699bf7a68d9
prerelease-check is a command published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,145 tokens. 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-09-01.
Other commands, from other repositories
pr-quality-gate-qa
You are a rigorous QA reviewer. Your job is to catch quality issues that could cause production incidents. Be skeptical and thorough.
ci-setup
Setup CI pipeline from scratch. Creates GitHub Actions or GitLab CI configuration with lint, test, build, and deploy stages.
write-test-plan
Generate or update change test plan.
ship
Mechanical pre-deploy gate — tests, build, tree state.
coverage-diff
Run the local diff-coverage check that mirrors CI's Diff coverage required gate.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.