gflow-cli CLAUDE.md

Session instructions for Claude Code, an AI coding assistant, working on the gflow-cli project. They explain which project files to read, where commands and skills live, and when to consult deeper documentation.

In plain words
What is it for?
Starting Claude Code sessions, finding project plans and documentation, handling authentication or saved assets, and preparing commits or releases.
Why use it?
They give the coding assistant the project context and session steps needed to follow the repository's rules consistently.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/ffroliva/gflow-cli/claude-md
Clone the repo
git clone --depth 1 https://github.com/ffroliva/gflow-cli
Per session 801 This file is loaded in full into every session.
When invoked 801 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00801 $0.00801
Opus 5 $0.00400 $0.00400
Sonnet 5 $0.00160 $0.00160
Haiku 4.5 $0.00080 $0.00080

Measured 2d ago against content hash be2f083475a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gflow-cli 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 2d 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.

CLAUDE.md · 45 lines

How it starts

The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

Project memory hub for Claude Code. The universal coding-agent rules for any tool (Cursor, Codex, Aider, Antigravity, etc.) live in AGENTS.md — this file carries Claude-Code-specific session protocol only.

What this project is

gflow-cli is an unofficial Python CLI that drives Google Flow (Veo image-to-video, Imagen text-to-image) from the terminal by reverse-engineering Flow's private REST API. See README.md for the user-facing overview.

On every session start

  1. Read AGENTS.md — universal rules every agent must follow.
  2. Read docs/INDEX.md — routing layer for all project docs and commands.
  3. Pull deeper context on demand:
    • Current task / where we left off → /gflow:status
    • Starting a new feature → /gflow:predict/gflow:scenario/gflow:plan <feature>
    • Touching auth or reCAPTCHA → /gflow:known-issues
    • Referencing a saved asset (@Name mention vs --ref/--reference-entity) → docs/REFERENCE_STRATEGIES.md
    • Cutting a release → /gflow:release
    • Before any commit → /gflow:check

Claude-Code-specific

  • Slash commands live under .claude/commands/gflow/ (all prefixed /gflow:).
  • Skills under skills/ are auto-discoverable; gflow-cli ships its own at skills/gflow-cli/SKILL.md.
  • Auto-memory at ~/.claude/projects/C--development-github-gflow-cli/memory/MEMORY.md carries cross-session feedback and project state.
  • Worktrees: the native EnterWorktree tool branches from origin/main (the default branch). Feature work integrates via develop — after entering a fresh worktree, immediately git switch -c <type>/<name> origin/develop and delete the auto-created worktree-* branch. On Windows, worktree removal can fail on a file lock (the worktree's .venv); git worktree prune + manual delete later is fine.

MCP GitHub tool — PR body rule (non-negotiable)

Read the full file on GitHub · 45 lines

Changes

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.

  1. 2d ago First seen · 45 lines · 801 tokens per session scan A be2f083475a6

Subscribe to this mod's changes

gflow-cli CLAUDE.md is an instructions file published in the GitHub repository ffroliva/gflow-cli (136 stars, last pushed 2d ago), licensed MIT. It adds 801 tokens to every session, about $0.0040 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.