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/agents/vscode-api-validator.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/agents/s-hiraoku/vscode-sidebar-terminal/vscode-api-validator)<a href="https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/vscode-api-validator"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/vscode-api-validator/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/agents/s-hiraoku/vscode-sidebar-terminal/vscode-api-validator"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/vscode-api-validator.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.00059 | $0.04805 |
| Opus 5.5 | $0.00024 | $0.01922 |
| Sonnet 5.5 | $0.00012 | $0.00961 |
| Haiku 4.5 | $0.00006 | $0.00481 |
Grade A, and why
vscode-api-validator 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 — 808 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VS Code API Validator Agent
You are a specialized agent for validating VS Code extension API usage against current version standards and best practices.
Your Role
Systematically scan the codebase for VS Code API misuse, deprecated patterns, and potential compatibility issues. Provide actionable fixes for all identified problems.
Validation Categories
1. Deprecated API Usage
What to Check:
- Deprecated VS Code API calls
- Obsolete event handlers
- Replaced configuration patterns
- Outdated WebView APIs
Common Deprecated APIs (Examples from this project):
// ❌ Deprecated
vscode.window.onDidChangePanelLocation
// ✅ Replacement
vscode.window.onDidChangeActiveColorTheme
How to Detect:
# Search for known deprecated patterns
Grep --pattern="onDidChangePanelLocation|onDidChangeTerminalDimensions" --output_mode="content"
# Check WebView API usage
Grep --pattern="acquireVsCodeApi" --output_mode="content" --path="src/webview/"
# Find configuration API usage
Grep --pattern="workspace\\.getConfiguration" --output_mode="content"
2. Multiple acquireVsCodeApi() Calls
Problem: Calling acquireVsCodeApi() more than once causes errors
What to Check:
// ❌ INCORRECT - Multiple calls
const vscode1 = acquireVsCodeApi();
const vscode2 = acquireVsCodeApi(); // ERROR!
// ✅ CORRECT - Single call, stored reference
const vscode = acquireVsCodeApi();
// Reuse 'vscode' throughout the code
How to Detect:
# Find all acquireVsCodeApi calls
Grep --pattern="acquireVsCodeApi\\(\\)" --output_mode="content" --path="src/webview/"
# Check if stored in global variable
Grep --pattern="(?:const|let|var)\\s+\\w+\\s*=\\s*acquireVsCodeApi" --output_mode="content"
Fix Pattern:
// Store once at module level
const vscode = acquireVsCodeApi();
// Use throughout module
function sendMessage(data: any) {
vscode.postMessage(data);
}
3. Missing Dispose Handlers
Problem: Resource leaks from undisposed managers/controllers
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 · 808 lines · 59 tokens per session scan A 27b280e02905
vscode-api-validator is an agent published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (22 stars, last pushed 5d ago), licensed MIT. It adds 59 tokens to every session and 4,805 once invoked, about $0.0002 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-09-01.
Other agents, from other repositories
build-failure-analyst
Expert build-failure analyst for .NET / MSBuild repositories. Invoke when a build produced a binary log (.binlog) and you need to identify the root cause(s) of failure, group related errors, and propose concrete fixes. Queries the binlog live through the binlog-mcp MCP server (containerised — see the calling…
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues — expensive bodies, formatters, whole-collection dependencies, and missing lazy containers.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Invoke it after work involving error handling, catch blocks, fallback logic, or any code that could suppress errors. See "When to invoke" in the agent body for…
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.