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-statusgit clone --depth 1 https://github.com/DVNghiem/FlowDeckWhat 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.00015 | $0.00822 |
| Opus 5 | $0.00008 | $0.00411 |
| Sonnet 5 | $0.00003 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
fd-status 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 3d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status
Show where the current task sits in the pipeline and what is blocking it.
Input: $ARGUMENTS — optional --topic=<slug> for a specific topic, --all to list
every topic in the project.
Default: active topic
Read ~/.fd-plan/<slug>/checkpoint.json first, falling back to
~/.fd-plan/<slug>/STATE.md. Resolve <topic> from --topic, else from topic in
STATE.md.
════════════════════════════════════════════════════════════
Project: <slug> Topic: <topic>
Updated: <timestamp> Source: checkpoint.json | STATE.md
────────────────────────────────────────────────────────────
Pipeline
✅ fd-task — artifacts confirmed
✅ fd-review — 0 blocking findings
🔄 fd-execute — wave-2 ← current
⬜ fd-verify
⬜ fd-done
────────────────────────────────────────────────────────────
Artifacts task.md ✅ architecture.md ✅ affect.md ✅ plan.md ✅
Plan <X> steps (<Y> complete)
Risk <low|medium|high> (from affect.md)
Worktrees <names, or "none">
Blockers <list, or "none">
════════════════════════════════════════════════════════════
Next: <next command in the pipeline>
Stage markers:
✅— recorded complete incheckpoint.jsonphases, or implied by STATE.md status🔄— the stage named bycurrent_command⬜— not yet reached⏭️— skipped, with the logged reason shown inline (trivial tasks only)
All topics (--all)
List every topic directory under ~/.fd-plan/<slug>/:
════════════════════════════════════════════════════
TOPICS — <slug>
════════════════════════════════════════════════════
✅ add-oauth-login — done | updated <time>
🔄 refactor-router — execute | updated <time> ← active
⬜ cache-invalidation — task | updated <time>
────────────────────────────────────────────────────
Total: 3 topics | 1 done | 1 in progress | 1 planned
════════════════════════════════════════════════════
Read each topic's stage from its artifacts on disk: plan.md present but no commits →
task; steps_complete non-empty → execute; STATE.md status: complete → done.
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.
- 3d ago First seen · 108 lines · 15 tokens per session scan A acd8f9bf4a11
fd-status is a command published in the GitHub repository DVNghiem/FlowDeck (24 stars, last pushed 14d ago), licensed MIT. It adds 15 tokens to every session and 822 once invoked, about $0.0001 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
annotate-plan
Draft a plan and open it in the annotator UI for user review.
wtfp:create-outline
Build the section structure, argument map, dependencies, and word budgets.
wtfp:checkpoint
Save, list, or restore an exact portable paper-state checkpoint.
wtfp:execute-outline
Draft independent section waves in parallel and verify cross-section coherence.
wtfp:pause-writing
Record an exact context handoff so another session can resume without reconstructing intent.
wtfp:resume-writing
Restore the latest portable handoff and route the researcher to the next safe action.