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 skills add marcus/sidecar --skill inline-editorgit 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/inline-editor)<a href="https://agentmods.dev/skills/marcus/sidecar/inline-editor"><img src="https://agentmods.dev/badge/skills/marcus/sidecar/inline-editor/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/marcus/sidecar/inline-editor"><img src="https://agentmods.dev/badge/skills/marcus/sidecar/inline-editor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 117 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00080 | $0.02485 |
| Opus 5.5 | $0.00032 | $0.00994 |
| Sonnet 5.5 | $0.00016 | $0.00497 |
| Haiku 4.5 | $0.00008 | $0.00248 |
Grade A, and why
inline-editor 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inline Editor Implementation
Overview
The inline editor (tmux_inline_edit) lets users edit files directly within the file browser preview pane using their preferred terminal editor (vim, nvim, nano, etc.) without leaving the TUI. The file tree remains visible during editing.
Core Principle: This is NOT a terminal emulator. Tmux manages the PTY backend; Sidecar acts as an input/output relay, similar to the workspace plugin's interactive mode.
Architecture
Components
- Entry Layer (
internal/plugins/filebrowser/inline_edit.go): Creates tmux sessions, manages editor lifecycle - Rendering Layer (
internal/plugins/filebrowser/view.go,inline_edit.go): Renders editor content within preview pane - Input Layer (
internal/plugins/filebrowser/plugin.go,mouse.go): Routes keys/clicks to editor or confirmation dialog - TTY Model (
internal/tty/tty.go): Handles tmux capture, cursor overlay, and input forwarding
Data Flow
User presses 'e' on file
-> enterInlineEditMode()
-> tmux new-session -d -s {sessionName} {editor} {path}
-> InlineEditStartedMsg
-> handleInlineEditStarted()
-> tty.Model.Enter()
-> Start polling tmux capture-pane
-> renderInlineEditorContent() in preview pane
-> User types -> tty.Model forwards to tmux
-> User exits -> SessionDeadMsg or exit keys
-> exitInlineEditMode()
-> Refresh preview
Key Files
| File | Purpose |
|---|---|
internal/plugins/filebrowser/inline_edit.go |
Editor lifecycle, confirmation dialog, dimension calculations |
internal/plugins/filebrowser/view.go |
Preview pane rendering, gradient border |
internal/plugins/filebrowser/mouse.go |
Click-away detection |
internal/plugins/filebrowser/plugin.go |
State management, Update routing |
internal/tty/tty.go |
TTY model for tmux interaction (shared with workspace) |
internal/app/update.go |
App-level key routing for inline edit context |
Critical Implementation Details
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 · 290 lines · 80 tokens per session scan A 294ef2fbe3fa
inline-editor is a skill published in the GitHub repository marcus/sidecar (1,091 stars, last pushed 11d ago), licensed MIT. It adds 80 tokens to every session and 2,485 once invoked, about $0.0003 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-30.
Other skills, from other repositories
revise-roadmap
Revise an implementation roadmap based on critic feedback.
build-knowledge-base
Build or update a persistent repo knowledge base graph.
research-codebase
Document codebase as-is through comprehensive research.
validate-phase-plan-structural
Per-phase plan structural validation gate - evaluates conformance to the concise vertical-slice phase-plan format.
implement
Execute an approved phase plan with TDD, dependency-aware task fan-out, required evidence, and a strict iteration handoff.
review-comments
Execute a feature-level review-comments cycle — aggregate unaddressed PR comments across every Feature.Repos PR, address or dismiss each one, and emit the standard handoff.