Borrowing it
Nothing to install: this file belongs to ffroliva/gflow-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ffroliva/gflow-cli/develop/.claude/commands/gflow/live-verify.mdgit clone --depth 1 https://github.com/ffroliva/gflow-cliWrote 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/ffroliva/gflow-cli/live-verify)<a href="https://agentmods.dev/commands/ffroliva/gflow-cli/live-verify"><img src="https://agentmods.dev/badge/commands/ffroliva/gflow-cli/live-verify/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/commands/ffroliva/gflow-cli/live-verify"><img src="https://agentmods.dev/badge/commands/ffroliva/gflow-cli/live-verify.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.00028 | $0.00094 |
| Opus 5.5 | $0.00011 | $0.00038 |
| Sonnet 5.5 | $0.00006 | $0.00019 |
| Haiku 4.5 | $0.00003 | $0.00009 |
Grade A, and why
live-verify 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 1mo 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.
What it actually says
/gflow:live-verify — Live-verification enforcement
Read skills/live-verify/SKILL.md and follow the protocol, passing $ARGUMENTS if given.
Do not call
Skill(skill="live-verify")— read the file directly.
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.
- 1mo ago First seen · 10 lines · 28 tokens per session scan A 587e6e4e8dd8
live-verify is a command published in the GitHub repository ffroliva/gflow-cli (337 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 94 once invoked, about $0.0001 per session on Opus 5.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
test
Run the app's microflow tests and verify it in the browser.
e2e-echo-command
E2E test command — echoes back the user message.
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; run or list flows…
qawolfCliRunResults.template
How to use what qawolf run get --run-id --json returns, and how to read the Playwright trace it links to.
validate-project
Validate the project with mxbuild and report the errors.
test-integration.en
Run the integration test workflow.