Sidecar is a terminal-based workspace for running AI coding agents alongside file trees, task issues, Git diffs, and Jira or GitHub resources in split panes. Developers use it to monitor agent sessions, inspect files and changes, manage workspaces, and handle tasks without leaving one shell. The catalogue entries extend or guide coding-agent workflows used with Sidecar.
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/marcus/sidecar/drag-panenpx skills add marcus/sidecar --skill drag-panegit clone --depth 1 https://github.com/marcus/sidecarWrote 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/marcus/sidecar/drag-pane)<a href="https://agentmods.dev/skills/marcus/sidecar/drag-pane"><img src="https://agentmods.dev/badge/skills/marcus/sidecar/drag-pane.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.00070 | $0.03202 |
| Opus 5 | $0.00035 | $0.01601 |
| Sonnet 5 | $0.00014 | $0.00640 |
| Haiku 4.5 | $0.00007 | $0.00320 |
Grade A, and why
drag-pane 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drag-to-Resize Pane Implementation
Overview
Add drag-to-resize support for two-pane plugin layouts (sidebar + main content). Users click and drag the divider between panes to resize them.
Prerequisites
- Plugin already has a two-pane layout (sidebar + main content)
- State persistence functions exist in
internal/state/state.go(each plugin has its own getter/setter) - Familiarity with
internal/mousepackage
Existing Implementations
| Plugin | State Functions | Mouse File |
|---|---|---|
| FileBrowser | GetFileBrowserTreeWidth() / SetFileBrowserTreeWidth() |
internal/plugins/filebrowser/mouse.go |
| GitStatus | GetGitStatusSidebarWidth() / SetGitStatusSidebarWidth() |
internal/plugins/gitstatus/mouse.go |
| Conversations | GetConversationsSideWidth() / SetConversationsSideWidth() |
internal/plugins/conversations/mouse.go |
| Workspace (project) | GetWorkspaceSidebarWidth() / SetWorkspaceSidebarWidth() |
internal/plugins/workspace/view_list.go |
| Sessions (global workspace) | GetWorkspaceSidebarWidth() / SetWorkspaceSidebarWidth() |
internal/overview/workspaces.go |
Windowing parity: project and global workspaces are one feature
The project workspace (internal/plugins/workspace) and the global Workspaces
browser shown as Sessions in the navbar (internal/overview) are two
projections of the same windowing model. They are not independent surfaces that
happen to look similar.
If a change affects panes, splits, drag handles, pane borders, focus chrome, or pane hit regions in one of them, it affects the other. The rule is structural, not a habit to remember:
internal/panelayoutowns pane-tree structure and geometry.internal/paneframeowns presentation: chrome geometry (Inset,Geometry), the leaf border states (Chrome,WrapLeaf), the drag handle (RenderDividerHandle,DividerHitBox,HandleStateFor), the compositor (Compose,ComposeLeaf,RenderContent), the chrome-aware floors (ChromeFloors), and the one order hit regions are registered in (RegisterRegions), and click-to-focus (LeafAt,FocusLeafAt).- Each surface implements
paneframe.Hostandpaneframe.RegionSinkin exactly one file:internal/plugins/workspace/pane_host.goandinternal/overview/pane_host.go.
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 · 384 lines · 70 tokens per session scan A aad5a0eab995
drag-pane is a skill published in the GitHub repository marcus/sidecar (1,049 stars, last pushed 4d ago), licensed MIT. It adds 70 tokens to every session and 3,202 once invoked, about $0.0003 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-30.
Other skills, from other repositories
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
frontend-screen
Default workflow for creating or redesigning a frontend screen, landing page, portfolio page, or responsive web section when visual direction and implementation fidelity matter.
designer
Visual + UX design defaults for new UIs. Material Design 3, dark/light theme, modern type, Behance-grade polish, i18n (en, pt-BR, es), context-aware favicon. No emojis and no em-dashes; use MD3/modern icons instead. Apply when building something new. Project conventions in .claude/conventions/web.md override these…
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
impeccable
Use when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable references and an optional upstream detector CLI.
figma-implement-design
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a…