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/.agents/skills/release/SKILL.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/skills/s-hiraoku/vscode-sidebar-terminal/release)<a href="https://agentmods.dev/skills/s-hiraoku/vscode-sidebar-terminal/release"><img src="https://agentmods.dev/badge/skills/s-hiraoku/vscode-sidebar-terminal/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/skills/s-hiraoku/vscode-sidebar-terminal/release"><img src="https://agentmods.dev/badge/skills/s-hiraoku/vscode-sidebar-terminal/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 50 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00033 | $0.00666 |
| Opus 5 | $0.00016 | $0.00333 |
| Sonnet 5 | $0.00007 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
release 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Version Update
Bump version and auto-generate CHANGELOG.md for the VS Code extension using standard-version.
Usage
/release <version-type>
Version Types
patch- Increment patch version (e.g., 0.3.1 → 0.3.2)minor- Increment minor version (e.g., 0.3.1 → 0.4.0)major- Increment major version (e.g., 0.3.1 → 1.0.0)
Workflow
Step 1: Read Current Version
node -p "require('./package.json').version"
Step 2: Check Unreleased Commits
Show commits since the last release tag to verify there are changes to release:
git log v$(node -p "require('./package.json').version")..HEAD --oneline
If there are no commits, warn the user and stop.
Step 3: Bump Version and Generate CHANGELOG
Use standard-version to bump version in package.json and package-lock.json, and auto-generate CHANGELOG.md from conventional commits:
npm run release:patch # for patch
npm run release:minor # for minor
npm run release:major # for major
This runs npx standard-version --release-as <type> which:
- Bumps version in
package.jsonandpackage-lock.json - Generates CHANGELOG.md entries from conventional commit messages
- Creates a commit with the changes
- Does NOT create a tag or push (configured in
.versionrc.cjs)
Step 4: Report Results
Display:
- Old version → New version
- CHANGELOG.md diff (new entries)
- Reminder: "Push with
git push, then create tag after CI passes"
Important Notes
- Do NOT create git tags — that is a separate step done after CI passes
- Do NOT push — the user decides when to push
- The
.versionrc.cjsconfig maps conventional commits to changelog sections:feat→ Addedfix→ Fixedperf,refactor,docs→ Changedrevert→ Revertedstyle,test,chore,ci→ hidden
File Locations
- Version:
package.json("version"field) - Lock file:
package-lock.json("version"field) - Changelog:
CHANGELOG.md - Config:
.versionrc.cjs
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 · 88 lines · 33 tokens per session scan A 09abcb503c4c
release is a skill published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 666 once invoked, about $0.0002 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-09-01.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.