Agent Deck is a terminal session manager that lets developers monitor and switch between multiple AI coding-agent sessions from one text interface. It helps people organize agents working across projects with groups, search, forking, Git worktrees, cost tracking, and a phone-controlled conductor. The catalogue entries extend its use with skills, commands, and a plugin.
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 asheshgoplani/agent-deck --skill recallgit clone --depth 1 https://github.com/asheshgoplani/agent-deckWrote 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/asheshgoplani/agent-deck/recall)<a href="https://agentmods.dev/skills/asheshgoplani/agent-deck/recall"><img src="https://agentmods.dev/badge/skills/asheshgoplani/agent-deck/recall/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/asheshgoplani/agent-deck/recall"><img src="https://agentmods.dev/badge/skills/asheshgoplani/agent-deck/recall.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.00000 | $0.03432 |
| Opus 5.5 | $0.00000 | $0.01373 |
| Sonnet 5.5 | $0.00000 | $0.00686 |
| Haiku 4.5 | $0.00000 | $0.00343 |
Grade A, and why
agent-deck-recall 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 26d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recall
Recall is agent-deck's memory of what every session was for and what
happened in it. Human intent (hints, tags) lives in the profile's state.db
and survives everything; the transcript index (recall.db) is disposable:
delete it, recall rebuild, nothing typed is lost. Full design:
docs/recall.md in the repo.
Phase 1 (available now): hints and tags
Hints are single-valued per key (setting a key again replaces it). Tags are a
set. Well-known keys: purpose, ticket, why, decision, outcome,
note, parent; any identifier-shaped key works.
At creation (add and launch)
agent-deck add . -c claude --hint purpose="fix flaky auth test" --ticket SB-412 --tag auth --tag flaky --why "3rd regression"
agent-deck launch . -c claude --ticket SB-412 -m "Fix the flaky auth test"
launchderivespurposefrom the first line of-mand both commands deriveparent=<parent id>for a child; an explicit--hint purpose=wins.conductor setup <name>recordspurpose=conductor <name>.--jsonechoeshintsandtags.
Afterwards (session annotate)
agent-deck session annotate <id> --decision "root cause was clock skew" --outcome worked --tag clock-skew
agent-deck session annotate <id> --set-hint ticket=SB-413 --remove-tag flaky --unset why
agent-deck session annotate --self --outcome worked # your own session (AGENTDECK_INSTANCE_ID)
agent-deck session annotate --self --note-stdin < summary.md # free-text note, 8 KiB cap
agent-deck session annotate <id> --json # read: hints, tags, harness links
End of task habit: before the completion sentinel, run
agent-deck session annotate --self --outcome <worked|failed|partial> --decision "<one line>"
so the next agent can find what you concluded.
Remote sessions
agent-deck remote <host> session annotate <id> --outcome worked
Runs on the remote and writes the remote's own state.db. Remote hints are never copied locally; read them through the same forwarded command.
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.
- 26d ago Changed · +82 lines d2f19dfadd4a
- 27d ago First seen · 178 lines · 0 tokens per session scan A 8fbabb4ea2a0
agent-deck-recall is a skill published in the GitHub repository asheshgoplani/agent-deck (1,098 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,432 tokens. 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-09-20.
Other skills, from other repositories
wiki-first-query
Wiki-first query convention: consult knowledge/wiki/index.md and the linked pages BEFORE re-reading raw sources for a project topic. The wiki is the canonical project memory layer.
memkernel-memory
MemKernel persistent memory protocol. Self-guarding: activates only when the memkernel MCP server is configured.
rosetta
Reconcile ALL prior agent conversations (Claude Code, Codex, Droid/Factory, Hermes, Cursor) with git history and docs into a cited ground truth, and distill durable decision records (ADRs/PDRs/BDRs). Use whenever the user wants to catch up on or get the state of a project, build or refresh a ground truth, read or mine…
past-sessions
Search and read past agent sessions on this machine — your own and other agents' — with agentcarto. Use when the user refers to earlier work ("what did we decide", "carry on from last time", "when did we touch this file"), or when the context you need is in a session rather than in the code.
gemini-md-improver
Audit and improve GEMINI.md files in repositories. Use when user asks to check, audit, update, improve, or fix GEMINI.md files. Scans for all GEMINI.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "GEMINI.md maintenance" or "project…
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.