Individual skill

agent-deck-session

Use at session start when Agent Deck MCP is configured or expected, including launch-selected sessions, or when the user asks for the deck status line / which deck is active.

plugins/not-so-fat/agent-deck/skills/agent-deck-session/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Agent Deck session opener

This skill verifies an MCP connection; it does not create one. In Codex, the Agent Deck
plugin's `.mcp.json` must already have launched `agent-deck mcp-launch`. The launcher reads
the folder's v3 assignment and sends the deck/workspace headers before these tools exist.

When Agent Deck MCP is configured for the current session, or `.agent-deck/use.json` indicates
that it is expected, this opener is a hard gate. The file is only one optional signal; the
gate also includes launch-selected sessions that deliberately have no assignment file.
Complete the opener before reading repository files, running task commands, or answering the
task. Once per conversation (or after the selected deck changes):

1. `get_session_context` — one call returns the workspace, effective deck,
   `display_summary`, services, credential metadata, and playbook summaries