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/terminal-research.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/terminal-research)<a href="https://agentmods.dev/commands/s-hiraoku/vscode-sidebar-terminal/terminal-research"><img src="https://agentmods.dev/badge/commands/s-hiraoku/vscode-sidebar-terminal/terminal-research/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/terminal-research"><img src="https://agentmods.dev/badge/commands/s-hiraoku/vscode-sidebar-terminal/terminal-research.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.00007 | $0.00684 |
| Opus 5 | $0.00003 | $0.00342 |
| Sonnet 5 | $0.00001 | $0.00137 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
terminal-research 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 10d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terminal Research Command
Research terminal implementation by invoking three specialized agents in parallel.
Execution Instructions
When this command is invoked with a query (e.g., /terminal-research How does VS Code handle IME?):
-
Launch three agents in parallel using a single message with multiple Task tool calls:
Agent 1: vscode-terminal-resolver
- Task description: "Analyze VS Code terminal implementation"
- Prompt: "Search the VS Code repository for how it handles: {ARGUMENTS}. Focus on terminal-related source code in src/vs/workbench/contrib/terminal/. Provide code references and implementation patterns."
Agent 2: serena-semantic-search
- Task description: "Search codebase semantically"
- Prompt: "Use Serena MCP to semantically search the current codebase for implementations related to: {ARGUMENTS}. Focus on terminal managers, WebView components, and xterm.js integrations. Provide file paths and line numbers."
Agent 3: xterm-info-analyzer
- Task description: "Get xterm.js documentation"
- Prompt: "Retrieve xterm.js documentation and best practices for: {ARGUMENTS}. Include API references, configuration options, and usage examples."
-
Wait for all agents to complete their tasks
-
Synthesize results into a comprehensive report with this structure:
## Terminal Research Results: {ARGUMENTS}
### VS Code Implementation
{vscode-terminal-resolver findings}
- Key patterns
- Code references (file:line)
### Current Codebase
{serena-semantic-search findings}
- Existing implementations
- File references (file:line)
### Xterm.js Best Practices
{xterm-info-analyzer findings}
- API documentation
- Configuration recommendations
### Synthesis & Recommendations
- Compare approaches (VS Code vs current vs xterm.js)
- Identify gaps or improvements
- Provide actionable next steps with code references
Example Usage
/terminal-research How does VS Code handle IME composition events?
/terminal-research What are xterm.js performance optimization techniques?
/terminal-research How should terminal process lifecycle be managed?
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.
- 10d ago First seen · 92 lines · 7 tokens per session scan A f53352680030
terminal-research is a command published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed 2d ago), licensed MIT. It adds 7 tokens to every session and 684 once invoked, about $0.0000 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 commands, from other repositories
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-13-4.en
Welcome to Lesson 13-4: Landing Page Implementation!
start-0-8
A Japanese-language command that displays the current project setup progress.