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/ffroliva/gflow-cli/llm-councilgit 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/llm-council)<a href="https://agentmods.dev/commands/ffroliva/gflow-cli/llm-council"><img src="https://agentmods.dev/badge/commands/ffroliva/gflow-cli/llm-council.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.00000 | $0.00436 |
| Opus 5 | $0.00000 | $0.00218 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
llm-council 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 4d 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:llm-council [PR# | --base <ref>] [--tier small|medium|high]
Read skills/llm-council/SKILL.md and follow its protocol now, treating $ARGUMENTS as: the PR number or --base <ref> (branch mode, same as /gflow:pr-council-review / /gflow:branch-review), plus --tier <small|medium|high> (default small). The high tier adds Antigravity (agy) alongside codex.
Do not call
Skill(skill="llm-council")orSkill(skill="pr-council-review")— the repo'sskills/*/SKILL.mdfiles are plain Markdown, not registered as Skill-tool-invocable (only.claude/commands/gflow/*are). Invoking either errors withUnknown skill: .... Read the files directly instead.
skills/llm-council/SKILL.md is the canonical body: tier resolution, the tool registry (fixed invocation recipes per external tool — read this before running any external tool, codex review in particular is a known trap), the availability-probe step, dispatch flow, and synthesis. It wraps skills/pr-council-review/SKILL.md unchanged for the internal dimension council.
Siblings: /gflow:pr-council-review <N> (internal-only, PR mode), /gflow:branch-review (internal-only, branch mode) — use either directly when external corroboration isn't warranted.
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.
- 4d ago First seen · 14 lines · 0 tokens per session scan A 593fe407513c
llm-council is a command published in the GitHub repository ffroliva/gflow-cli (143 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 436 tokens. 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
diff-script
Compare an MDL script against the project's current state.
toh-help
Display all Toh Framework commands and quick usage guide.
doctor
Run procedural readiness checks for goal-flight.
pipeline-undo
Undo a pipeline run's result. With worktree isolation (the current engine), this is clean and low-risk: a run never touches your checkout — its result lives only on a pipeline/ branch (and, for a --push run, on the remote). "Undo" therefore means deleting that branch and its worktree, not reverting your working tree.
respond-to-issue
Respond to an issue triggered by @elixpoo mention or the ELIXPO label.
elite-review
Run an elite, high-scrutiny Claude review against the current git workspace.