Borrowing it
Nothing to install: this file belongs to malwarebo/nyrve. 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/malwarebo/nyrve/main/.github/skills/agent-sessions-layout/SKILL.mdgit 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/agent-sessions-layout)<a href="https://agentmods.dev/skills/malwarebo/nyrve/agent-sessions-layout"><img src="https://agentmods.dev/badge/skills/malwarebo/nyrve/agent-sessions-layout/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/skills/malwarebo/nyrve/agent-sessions-layout"><img src="https://agentmods.dev/badge/skills/malwarebo/nyrve/agent-sessions-layout.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.00051 | $0.01095 |
| Opus 5.5 | $0.00020 | $0.00438 |
| Sonnet 5.5 | $0.00010 | $0.00219 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
agent-sessions-layout 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When working on the Agent Sessions workbench layout, always follow these guidelines:
1. Read the Specification First
The authoritative specification for the Agent Sessions layout lives at:
src/vs/sessions/LAYOUT.md
Before making any changes to the layout code, read and understand the current spec. It defines:
- The fixed layout structure (grid tree, part positions, default sizes)
- Which parts are included/excluded and their visibility defaults
- Titlebar configuration and custom menu IDs
- Editor modal overlay behavior and sizing
- Part visibility API and events
- Agent session part classes and storage keys
- Workbench contributions and lifecycle
- CSS classes and file structure
2. Keep the Spec in Sync
If you modify the layout implementation, you must update LAYOUT.md to reflect those changes. The spec should always match the code. This includes:
- Adding/removing parts or changing their positions
- Changing default visibility or sizing
- Adding new actions, menus, or contributions
- Modifying the grid structure
- Changing titlebar configuration
- Adding new CSS classes or file structure changes
Update the Revision History table at the bottom of LAYOUT.md with a dated entry describing what changed.
3. Implementation Principles
When proposing or implementing changes, follow these rules from the spec:
- Maintain fixed positions — Do not add settings-based position customization
- Panel must span the right section width — The grid structure places the panel below Chat Bar and Auxiliary Bar only
- Sidebar spans full height — Sidebar is in the main content branch, spanning from top to bottom
- New parts go in the right section — Any new parts should be added to the horizontal branch alongside Chat Bar and Auxiliary Bar
- Preserve no-op methods — Unsupported features (zen mode, centered layout, etc.) should remain as no-ops, not throw errors
- Handle pane composite lifecycle — When hiding/showing parts, manage the associated pane composites
- Use agent session parts — New part functionality goes in the agent session part classes (
SidebarPart,AuxiliaryBarPart,PanelPart,ChatBarPart,ProjectBarPart), not the standard workbench parts - Use separate storage keys — Agent session parts use their own storage keys (prefixed with
workbench.agentsession.orworkbench.chatbar.) to avoid conflicts with regular workbench state - Use agent session menu IDs — Actions should use
Menus.*menu IDs (fromsessions/browser/menus.ts), not sharedMenuId.*constants
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 · 84 lines · 51 tokens per session scan A 2de984ee0e97
agent-sessions-layout is a skill published in the GitHub repository malwarebo/nyrve (5 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 1,095 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-08-31.
Other skills, from other repositories
bb-theme-authoring
Create or edit BB color themes and inspect them in the Theme Preview panel.
agent-annotations
Create or edit element annotations in desktop Browser tabs, or update saved annotation comments through the plugin RPC.
canvas
Author Nimbalyst Project Canvas boards (.canvas files) — an infinite canvas whose cards are live editors for real workspace files and shared documents, arranged spatially and wired with edges. Use when the user asks for a canvas, a board, a spatial layout of documents or mockups, a flow of screens, or a workspace…
datamodellm
Create visual data models for database schemas using Nimbalyst's DataModelLM editor. Use when the user wants to design a data model, database schema, entity relationship diagram, or Prisma schema.
mockuplm
Create visual UX mockups using HTML/CSS files (.mockup.html). Use when the user wants to design UI, wireframes, visual layouts, or plan features visually.
excalidraw
Create diagrams and visual drawings using Excalidraw (.excalidraw files). Use when the user wants flowcharts, architecture diagrams, system diagrams, sketches, or any visual diagram. For database schemas and entity relationship diagrams, use the DataModelLM extension instead.