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/issue-assessmentgit clone --depth 1 https://github.com/ffroliva/gflow-cliWhat 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.00092 | $0.00375 |
| Opus 5 | $0.00046 | $0.00187 |
| Sonnet 5 | $0.00018 | $0.00075 |
| Haiku 4.5 | $0.00009 | $0.00038 |
Grade A, and why
issue-assessment 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.
What it actually says
/gflow:issue-assessment [issue number or URL]
Read skills/issue-assessment/SKILL.md and follow its protocol now, passing $ARGUMENTS as the issue to assess.
Do not call
Skill(skill="issue-assessment")— the repo'sskills/*/SKILL.mdfiles are plain Markdown, not Skill-tool-invocable (only.claude/commands/gflow/*are). Read the file directly instead.
The skill at skills/issue-assessment/SKILL.md ingests the issue, verifies the
claim (dispatching a search agent to keep context clean), assigns one verdict,
applies the e2e-gate (never claim a fix is verified on an unverifiable
surface), and emits a standard report artifact. On a CONFIRMED / LIKELY-BUG
verdict with localized, verifiable scope it hands off to issue-resolve;
otherwise it replies only.
Typical chain:
/gflow:issue-assessment <N> → verdict + e2e-gate + reply artifact
↓ (if scope clear & verifiable)
issue-resolve <N> → worktree + TDD + draft PR for human review
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.
- 2d ago First seen · 29 lines · 92 tokens per session scan A 7b8621092c52
issue-assessment is a command published in the GitHub repository ffroliva/gflow-cli (136 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 375 once invoked, about $0.0005 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 commands, from other repositories
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
diff-script
Compare an MDL script against the project's current state.
toh-help
Display all Toh Framework commands and quick usage guide.
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.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
doctor
Validate, install, and update Hydraia's external dependencies (codegraph, markitdown, E2E browser binaries).