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 instructions/eyalbpm/sessiondeck/claude-mdgit clone --depth 1 https://github.com/eyalBPM/SessionDeckWhat 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.02068 | $0.02068 |
| Opus 5 | $0.01034 | $0.01034 |
| Sonnet 5 | $0.00414 | $0.00414 |
| Haiku 4.5 | $0.00207 | $0.00207 |
Grade A, and why
SessionDeck CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SessionDeck — working notes for Claude Code
A WPF (.NET 10, Windows-only) control deck for Claude Code sessions. The UI and the CLI
are the same exe: launched with no arguments it raises the window plus a named-pipe
server (\\.\pipe\sessiondeck); launched with arguments it acts as a client against the
running instance. A companion VSCode extension (vscode-extension/) reports tabs and the
git branch over that pipe and opens sessions on request.
Public-facing overview: README.md. Hook wiring, the waiting-detection
thresholds and the toggles: hooks/README.md — that file is the
authoritative source Cli/HookInstaller.cs must match exactly.
Build, run, deploy
The running app locks its own exe. Building over a live instance fails with MSB3027. Always:
.\bin\Debug\net10.0-windows\SessionDeck.exe quit # graceful — releases the AppBar
Start-Sleep -Milliseconds 1500
dotnet build -c Debug
Start-Process .\bin\Debug\net10.0-windows\SessionDeck.exe
Never Stop-Process -Force: the Reserved Zone is released in OnClosing only, and a
forced kill leaves Windows' work area permanently shrunk with no way for the user to
tell why.
To compile without touching a running instance (a syntax check that skips the copy step):
dotnet msbuild SessionDeck.csproj -t:Compile -p:Configuration=Debug -v:m
WinExe means CLI output only reaches a parent console through
AttachConsole(ATTACH_PARENT_PROCESS) — expect no captured stdout from tooling.
Tests
powershell -NoProfile -ExecutionPolicy Bypass -File .\tests\install-hooks.tests.ps1 -Exe <path to SessionDeck.exe>
38 cases over the install-hooks / uninstall-hooks merge: a missing settings file, an
empty one, hooks from an old path, another tool's hooks on the same event, malformed
JSON, a second run in a row, dry-run, and a shared group where only our entry may be
removed. Run it against the exe you actually built.
These tests passing does not mean the status lifecycle works. They cover the installer only. A card can stay blue, blink wrongly or go quiet while all 38 pass — see "Debugging status and blink" below.
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.
- yesterday First seen · 148 lines · 2,068 tokens per session scan A 1cac54dc0082
SessionDeck CLAUDE.md is an instructions file published in the GitHub repository eyalBPM/SessionDeck (1 stars, last pushed 24d ago), licensed MIT. It adds 2,068 tokens to every session, about $0.0103 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 instructions, from other repositories
Pawse CLAUDE.md
Claude Code instructions for slnu21/Pawse, covering claude.md, what this is, commands, manual gui test — pipe a sample hook json to one event and syntax check without running.
hana-developer-cli-tool-example mcp-server-development.instructions.md
Use when creating or updating MCP (Model Context Protocol) server components. Enforces TypeScript patterns, JSON-RPC communication rules, tool/resource/prompt registration, and integration with CLI command metadata. Ensures MCP server follows protocol requirements and maintains consistency with the CLI infrastructure.
hana-developer-cli-tool-example connection-pooling-timeout-management.instructions.md
Use when creating or updating code that manages database connections. Enforces consistent timeout configuration, proper connection cleanup, graceful error handling, and connection pooling best practices across CLI commands, routes, and tests.
coder CLAUDE.md
Claude Code instructions for coder/coder, a project described as: Secure environments for developers and their agents.
mcec AGENTS.md
Instructions for tig/mcec, covering agents.md: driving (and testing) mcec with an agent, the built-in guidance (single source of truth), security (do not regress), dogfood: test mcec using mcec (mcec drives mcec) and operational tips (learned the hard way).
hana-developer-cli-tool-example hana-cli-usage.instructions.md
Use when working with SAP HANA databases, CDS models, HDI containers, or BTP projects. Provides hana-cli command knowledge for database operations.