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.
npx agentmods add skills/malwarebo/nyrve/sessionsnpx skills add malwarebo/nyrve --skill sessionsgit clone --depth 1 https://github.com/malwarebo/nyrveWrote 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/malwarebo/nyrve/sessions)<a href="https://agentmods.dev/skills/malwarebo/nyrve/sessions"><img src="https://agentmods.dev/badge/skills/malwarebo/nyrve/sessions.svg" alt="Measured on agentmods" 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 | $0.00045 | $0.03898 |
| Opus 5 | $0.00023 | $0.01949 |
| Sonnet 5 | $0.00009 | $0.00780 |
| Haiku 4.5 | $0.00005 | $0.00390 |
Grade A, and why
sessions 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 4d 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When working on the Agent Sessions window (src/vs/sessions/), always follow these guidelines:
1. Read the Specification Documents First
The src/vs/sessions/ directory contains authoritative specification documents. Always read the relevant spec before making changes.
| Document | Path | Covers |
|---|---|---|
| Layer spec | src/vs/sessions/README.md |
Layering rules, dependency constraints, folder conventions |
| Layout spec | src/vs/sessions/LAYOUT.md |
Grid structure, part positions, sizing, CSS classes, API reference |
| AI Customizations | src/vs/sessions/AI_CUSTOMIZATIONS.md |
AI customization editor and tree view design |
| Chat Widget | src/vs/sessions/browser/widget/AGENTS_CHAT_WIDGET.md |
Chat widget wrapper architecture, deferred session creation, option delivery |
If you modify the implementation, you must update the corresponding spec to keep it in sync. Update the Revision History table at the bottom of LAYOUT.md with a dated entry.
2. Architecture Overview
2.1 Layering
vs/base ← Foundation utilities
vs/platform ← Platform services
vs/editor ← Text editor core
vs/workbench ← Standard VS Code workbench
vs/sessions ← Agent Sessions window (this layer)
Key constraint: vs/sessions may import from vs/workbench and all layers below it. vs/workbench must never import from vs/sessions.
2.2 Dependency Rules
- ✅ Import from
vs/base,vs/platform,vs/editor,vs/workbench - ✅ Import within
vs/sessions(internal) - ❌ Never import
vs/sessionsfromvs/workbench - Run
npm run valid-layers-checkto verify layering
2.3 How It Differs from VS Code
| Aspect | VS Code Workbench | Agent Sessions Window |
|---|---|---|
| Layout | Configurable part positions | Fixed layout, no settings customization |
| Chrome | Activity bar, status bar, banner | Simplified — none of these |
| Primary UX | Editor-centric | Chat-first (Chat Bar is a primary part) |
| Editors | In the grid layout | Modal overlay above the workbench |
| Titlebar | Menubar, editor actions, layout controls | Session picker, run script, toggle sidebar/panel |
| Navigation | Activity bar with viewlets | Sidebar (views) + sidebar footer (account) |
| Entry point | vs/workbench workbench class |
vs/sessions/browser/workbench.ts Workbench class |
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.
- 4d ago First seen · 310 lines · 45 tokens per session scan A 074e69e9e0fa
sessions is a skill published in the GitHub repository malwarebo/nyrve (5 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 3,898 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-08-31.
Other skills, from other repositories
skill-creator
Create new bb skills and improve existing ones. Use whenever a user asks to create, write, edit, refine, test, or optimize a skill; turn a workflow into a reusable skill; fix skill triggering; or improve a SKILL.md file.
docs
Access and update the user's Docs vaults. Use whenever the user asks to read, find, create, update, or store a note, document, plan, or HTML artifact; when a Docs @-mention appears in context; or when an answer should link to a document the user can open in Docs.
plugin-guide-maintenance
Keep the Plugin Guide aligned with public Plugin SDK changes that affect its documented contract. Use this skill when an addition, change, rename, stabilization, or removal in @get-bb/plugin-sdk, app.slots., or BbPluginApi changes a Guide card, API symbol list, fixture, or SDK inventory. Do not use it for internal API…
memory
Use durable BB memory when prior project knowledge or cross-project user preferences can improve the current task, and save durable new learning through the bb memory CLI.
workflows
Execute a workflow script that orchestrates multiple subagents deterministically. Use when the user explicitly requests a workflow, multi-agent orchestration, parallel or sequential agent pipelines, structured agent outputs, or a durable background workflow run.
submit-a-plugin
Submit a bb plugin to the BB Community marketplace. Use whenever a user asks to submit, list, publish, or add a plugin to the BB marketplace, or asks for a marketplace pull request. This skill validates the plugin and release, creates the marketplace entry and icon, and opens the pull request.