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 commands/dvnghiem/flowdeck/fd-resumegit clone --depth 1 https://github.com/DVNghiem/FlowDeckWrote 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/commands/dvnghiem/flowdeck/fd-resume)<a href="https://agentmods.dev/commands/dvnghiem/flowdeck/fd-resume"><img src="https://agentmods.dev/badge/commands/dvnghiem/flowdeck/fd-resume.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.00030 | $0.00828 |
| Opus 5 | $0.00015 | $0.00414 |
| Sonnet 5 | $0.00006 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
fd-resume 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume
Resume a previously interrupted FlowDeck session.
Input: $ARGUMENTS — pass --yes to skip the confirmation pause.
Steps
-
Read
~/.fd-plan/<slug>/checkpoint.json— this is the primary source.- If present and
versionis"1": rebuild the session summary fromcurrent_command,current_stage,topic,phases,worktrees, andblockers. - If absent, unreadable, or carrying a
versionthis command does not understand: fall back to~/.fd-plan/<slug>/STATE.mdand log which source was used.
- If present and
-
If
checkpoint.jsonis missing, fall back toSTATE.md.- Read
topic,status,plan_confirmed,steps_complete,last_action,next_actionto reconstruct where the session stopped. - If
STATE.mdis also missing, error:"No planning workspace. Run /fd-task to start."
- Read
-
Read
STATE.mdto fill in anythingcheckpoint.jsondoes not carry:last_updated,plan_confirmed,steps_complete. -
Read
~/.fd-plan/<slug>/<topic>/plan.mdif it exists — show a preview (first 20 lines). -
Read
~/.fd-plan/<slug>/<topic>/task.mdif it exists — show the requirement count. -
Present the session summary:
═══════════════════════════════════════════════
RESUMING SESSION
═══════════════════════════════════════════════
Source: checkpoint.json | STATE.md (fallback)
Project: <slug> | Topic: <topic>
Command: <current_command> → stage: <current_stage>
Status: <status>
Phases: 1 complete, 2 in_progress, 3 pending
Last updated: <timestamp>
Plan confirmed: <yes/no>
Requirements: <X> from task.md
Worktrees: <names, or "none">
Blockers: <list, or "none">
Plan preview:
<first 10 lines of plan.md>
───────────────────────────────────────────────
Type CONFIRM to resume execution from this point.
═══════════════════════════════════════════════
-
Unless
--yesis passed, PAUSE and wait for the user to type CONFIRM. -
After confirmation, resume from
current_commandatcurrent_stage:- Re-enter
current_commandand skip forward tocurrent_stage— do not replay stages already recorded complete inphases. - If
blockersis non-empty, report them and stop. Do not resume into a blocked state. - If
worktreesis non-empty, list them and confirm whether to reuse or recreate before continuing. - If
checkpoint.jsonwas absent, use the STATE.md path: whenplan_confirmed: trueandplan.mdhas uncompleted steps, resume at/fd-execute; when no plan exists, start at/fd-task. - Brief the user on the next step before starting it.
- Re-enter
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 · 95 lines · 30 tokens per session scan A 6a1983e4382a
fd-resume is a command published in the GitHub repository DVNghiem/FlowDeck (24 stars, last pushed 16d ago), licensed MIT. It adds 30 tokens to every session and 828 once invoked, about $0.0002 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 commands, from other repositories
md
Open a Markdown file in the browser-based annotator for review.
annotate:md
Annotate a markdown file in the browser.
switch
Switch your campy pet (cat, hamster, ghost, robot, dragon, turtle, panda, dog).
pet
Pet your campy pet to boost happiness.
play
Play with your campy pet to boost happiness.
campy
Show your campy pet's current status.