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 skills/ffroliva/gflow-cli/doc-reviewnpx skills add ffroliva/gflow-cli --skill doc-reviewgit 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/doc-review)<a href="https://agentmods.dev/skills/ffroliva/gflow-cli/doc-review"><img src="https://agentmods.dev/badge/skills/ffroliva/gflow-cli/doc-review.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.00058 | $0.04108 |
| Opus 5 | $0.00029 | $0.02054 |
| Sonnet 5 | $0.00012 | $0.00822 |
| Haiku 4.5 | $0.00006 | $0.00411 |
Grade A, and why
doc-review 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gflow:doc-review — Documentation Review Gate
Run this gate before cutting a release. Two phases:
- Mechanical checks (sections 1–7 below) — fast, scripted, deterministic. Run inline.
- LLM council audit (section 8) — 3 parallel review subagents, then consensus synthesis. The mechanical pass catches stale strings and dead links; the council catches drift between docs, fictional claims, and gaps a human reader would notice.
Every item reports PASS / UPDATED / WARN / FAIL. Any FAIL or any RED council verdict blocks the release.
Provenance: the council protocol below was validated on the v0.8.1 docs refresh release (2026-05-23). The audit found 11 fixable issues that the mechanical checklist alone missed (e.g., the
experimental/subpackage fiction in 3 files, thegflow video i2vnon-working hero snippet in README). Keep the council step — it pays for itself.
0 · Pre-flight
- Confirm you are on the release branch (
release/vX.Y.Zorhotfix/...), not ondevelopormain. - If a release spec exists at
docs/superpowers/specs/YYYY-MM-DD-*-design.md, identify it now — the council auditors will use it as the ground truth for "what was supposed to ship." - If there is no spec, that is also fine — the council will work from the docs alone, but flag the absence as a process risk.
1 · Version references
Check these files for stale version strings (old numbers, outdated status labels):
| File | What to verify |
|---|---|
README.md |
Status badge, "Project status" section, install example |
AGENTS.md |
Module list, exit-code range, dev-environment commands |
llms.txt |
Header summary (Python version, stable surface claims) |
CLAUDE.md |
"Active phase" pointer if present |
PLAN.md |
Phase status (IN PROGRESS / DONE) and version annotations |
KNOWN_ISSUES.md |
Open entries resolved by this release → move to Resolved with evidence |
CHANGELOG.md |
[Unreleased] empty; link footer matches new version |
pyproject.toml + src/gflow_cli/__init__.py |
Both set to the new version |
docs/PROJECT_STATUS.md |
"Current release" subsection + milestone-history row for this version |
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 · 348 lines · 58 tokens per session scan A 6535bf52cf08
doc-review is a skill published in the GitHub repository ffroliva/gflow-cli (136 stars, last pushed 3d ago), licensed MIT. It adds 58 tokens to every session and 4,108 once invoked, about $0.0003 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 skills, from other repositories
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
repomix
Pack and analyze codebases into AI-friendly single files using Repomix. Use when the user wants to explore repositories, analyze code structure, find patterns, check token counts, or prepare codebase context for AI analysis. Supports both local directories and remote GitHub repositories.
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.
pr-feedback
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.
potpie-source-ingestion
Use when the user explicitly asks to ingest, refresh, or deeply understand a repository, PR, issue, ticket, runbook, incident report, document, or web link into Potpie. The harness performs todo-driven discovery, uses local/GitHub/integration tools and read-only subagents when available, builds evidence-backed…
finding-protocol
Operational-tier finding template — minimal fields for sub-agent decision support. Heavyweight deliverable promotion lives in skills/decepticon/final-report.