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 ffroliva/gflow-cli --skill live-verifygit 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/skills/ffroliva/gflow-cli/live-verify)<a href="https://agentmods.dev/skills/ffroliva/gflow-cli/live-verify"><img src="https://agentmods.dev/badge/skills/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/skills/ffroliva/gflow-cli/live-verify"><img src="https://agentmods.dev/badge/skills/ffroliva/gflow-cli/live-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 100 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00100 | $0.02342 |
| Opus 5.5 | $0.00040 | $0.00937 |
| Sonnet 5.5 | $0.00020 | $0.00468 |
| Haiku 4.5 | $0.00010 | $0.00234 |
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.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gflow:live-verify — Live-verification enforcement
gflow-cli reverse-engineers a blackbox: Google Flow. Offline checks (ruff, pyright,
unit/BDD tests) verify gflow-cli's own code does what it's supposed to; they cannot verify
Flow still behaves the way it was captured, because Flow is external and changes without
notice (see #174). This gate enforces two
things, both evidence-based (no claim without a fresh verification artifact — see the
superpowers:verification-before-completion skill):
- Part 1 — Pre-flight, at the start of feature/fix work: confirm the checkout reflects
current
developbefore investing effort. - Part 2 — Live-verify, before claiming done (after
/code-reviewand/ponytail:ponytail-review, before commit/PR): exercise the change against real Flow.
Full design rationale:
docs/superpowers/specs/2026-07-19-live-verify-design.md.
Part 1 — Pre-flight
Run before writing any code for a new feature/fix:
git fetch origin
git rev-parse --abbrev-ref HEAD
git rev-list --count HEAD..origin/develop
git log --oneline -5
git rev-list --count HEAD..origin/develop is an asymmetric DAG set-difference — it counts
commits develop has that the current HEAD lacks, regardless of HEAD's own private
unmerged history. This is what catches a genuinely diverged stale branch, not just a
behind-by-fast-forward one.
- If the count is nonzero: stop.
git pull(ondevelop) or rebase/merge (on a feature branch) before continuing. - If the branch's last real commit looks old relative to recent
developactivity (a smell for stale WIP — e.g. missing a function/guard thatdevelopalready has): stop and surface it. Don't silently proceed, don't silently switch — name the divergence and ask the user how to proceed. - A separate sibling checkout is not itself a red flag — this project's workflow
routinely uses sibling checkouts for isolated feature branches, and a real feature branch
is supposed to differ from
develop. The actual signal is "differs fromdevelopin a way that suggests staleness" (missing somethingdevelophas), not "differs by adding new work on top of it." When in doubt, diff the specific file(s) about to be touched againstorigin/develop's version before assuming they match:
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 Changed · +6 lines 4867fcbc6a70
- 1mo ago Changed · +8 lines 69ce0c036cc3
- 1mo ago First seen · 152 lines · 100 tokens per session scan A faf0af13961a
live-verify is a skill published in the GitHub repository ffroliva/gflow-cli (345 stars, last pushed today), licensed MIT. It adds 100 tokens to every session and 2,342 once invoked, about $0.0004 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 skills, from other repositories
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.
tmux-real-user-testing
A real-user test workflow for Qwen Code's terminal interface, using tmux to drive the program and capture readable screen snapshots. tmux is a tool for running and observing terminal sessions.
agent-reproduce-align
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
deflake
Stabilize a flaky test with a minimal, assertion-preserving fix — never by weakening or deleting the check.