What is vscode-sidebar-terminal AGENTS.md?

Repository instructions for coding agents working on a VS Code extension, including its development flow, project structure, tests, and build commands.

Use them when modifying the extension, especially when writing tests first, working on planning proposals, or running the project's build and test checks.

They give an agent the project's local rules so changes follow its required process and organization.

How s-hiraoku/vscode-sidebar-terminal configures Codex and OpenCode

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/s-hiraoku/vscode-sidebar-terminal/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminal

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/s-hiraoku/vscode-sidebar-terminal/agents-md/github.svg)](https://agentmods.dev/instructions/s-hiraoku/vscode-sidebar-terminal/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/s-hiraoku/vscode-sidebar-terminal/agents-md"><img src="https://agentmods.dev/badge/instructions/s-hiraoku/vscode-sidebar-terminal/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/s-hiraoku/vscode-sidebar-terminal/agents-md"><img src="https://agentmods.dev/badge/instructions/s-hiraoku/vscode-sidebar-terminal/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 717 This file is loaded in full into every session.

When invoked 717 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00717	$0.00717
Opus 5	$0.00358	$0.00358
Sonnet 5	$0.00143	$0.00143
Haiku 4.5	$0.00072	$0.00072

Measured 6d ago against content hash 5638fefe21c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

vscode-sidebar-terminal AGENTS.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 6d 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.

AGENTS.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Development Flow (Mandatory)

When receiving a feature request or modification, write tests first
Present the tests to confirm the specification
Proceed to implementation only after confirmation
Adjust implementation until all tests pass

OpenSpec Instructions

These instructions are for AI assistants working in this project.

Always open @/openspec/AGENTS.md when the request:

Mentions planning or proposals (words like proposal, spec, change, plan)
Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
Sounds ambiguous and you need the authoritative spec before coding

Use @/openspec/AGENTS.md to learn:

How to create and apply change proposals
Spec format and conventions
Project structure and guidelines

Keep this managed block so 'openspec update' can refresh the instructions.

Repository Guidelines

Project Structure & Module Organization

Extension entry point is src/extension.ts; feature code is grouped beneath src/core/, src/terminals/, src/sessions/, and src/webview/.
Test suites mirror runtime folders under src/test/ and share fixtures via src/test/shared/.
Bundled JavaScript emits to out/, releases land in dist/, assets stay in resources/, and telemetry directories (coverage/, report/, temp_out/) remain read-only.

Build, Test, and Development Commands

npm run compile performs a webpack build; npm run watch rebuilds on change.
npm run lint and npm run format enforce ESLint plus Prettier before committing.
Use npm run test:unit, npm run test:integration, and npm run test:all as the quick-to-full Vitest ladder.
npm run test:coverage keeps v8 coverage thresholds (70% lines/functions, 60% branches) satisfied.
npm run package emits the .vsix bundle.

Coding Style & Naming Conventions

TypeScript uses 2-space indentation, camelCase for variables/functions, PascalCase for classes, and avoids any in favor of explicit VS Code types.
Centralize enums, literals, and contracts in src/core/constants/ and src/core/types/; keep terminal logic inside src/terminals/.
Run npm run format before commits so imports and whitespace stay canonical; ESLint blocks unused imports and unsafe async patterns.

Read the full file on GitHub · 63 lines

Changes

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.

6d ago First seen · 63 lines · 717 tokens per session scan A 5638fefe21c2

Subscribe to this mod's changes

vscode-sidebar-terminal AGENTS.md is an instructions file published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed 2d ago), licensed MIT. It adds 717 tokens to every session, about $0.0036 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-03.

Building agents Testing

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.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

vscode-sidebar-terminal: Instructions file for Codex