agentmods.dev

Sessions Window Developer

A specialist role for developing the Agent Sessions Window, a VS Code area for working with agent sessions.

In plain words
What is it for?
Use it when modifying the Agent Sessions Window, especially code under src/vs/sessions.
Why use it?
It keeps related changes focused in the sessions code and directs developers to the relevant architecture guidance.

Agent

5 2mo ago A scan 12 tokens original MIT
View the source file malwarebo/nyrve
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/malwarebo/nyrve/sessions
Clone the repo
git clone --depth 1 https://github.com/malwarebo/nyrve
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 151 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00151
Opus 5 $0.00006 $0.00076
Sonnet 5 $0.00002 $0.00030
Haiku 4.5 $0.00001 $0.00015

Measured yesterday against content hash 56e6a353f471, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Sessions Window Developer 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 yesterday.

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.

.github/agents/sessions.md · 16 lines

What it actually says

Role and Objective

You are a developer working on the 'sessions window'. Your goal is to make changes to the sessions window (src/vs/sessions), minimally editing outside of that directory.

Instructions

  1. Always read the sessions skill first. This is your primary source of truth for the sessions architecture.
    • Invoke skill: "sessions".
  2. Focus your work on src/vs/sessions/.
  3. Avoid making changes to core VS Code files (src/vs/workbench/, src/vs/platform/, etc.) unless absolutely necessary for the sessions window functionality.
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.

  1. yesterday First seen · 16 lines · 12 tokens per session scan A 56e6a353f471

Subscribe to this mod's changes

Sessions Window Developer is an agent published in the GitHub repository malwarebo/nyrve (5 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 151 once invoked, about $0.0001 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-08-31.

ai-agentsclaude-codeide
Related

Other agents, from other repositories

agent-provider-architecture

This document is a reference for implementing a new agent provider in Nimbalyst. It is the architectural counterpart to docs/AIPROVIDERTYPES.md (which is end-user / product oriented) and walks through every seam a new agent has to fit through: session start and resume, prompt handling, transcript output, tool calling…

nimbalyst/nimbalyst · 0 tokens

codex-pre-edit-tracking-investigation

Status: STUCK. Three approaches tried, none reliably solves the pre-edit race for update-kind filechange items. This doc captures everything learned so the next session can pick up cleanly without re-deriving.

nimbalyst/nimbalyst · 0 tokens

tasks-to-chats-migration

The Tasks API (/api/v2/tasks) and the Chats API (/api/v2/chats) serve similar goals (programmatic access to AI-powered coding agents) but they differ significantly in architecture, capabilities, and usage patterns.

coder/coder · 0 tokens

index

Coder Agents is a chat interface and API for delegating development work and research to coding agents in your Coder deployment. Developers describe the work they want done, and Coder Agents handles selecting a template, provisioning a workspace, and executing the task.

coder/coder · 0 tokens

chat-search-syntax

The chat list endpoint accepts a q query parameter for filtering conversations. All filters use key:value syntax. Bare search terms are rejected; use title: for title filtering or search: for full-text search.

coder/coder · 0 tokens

Plan

A desktop app for isolated, parallel agentic development.

coder/xum · 1 tokens