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/issue-assessment.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/issue-assessment)<a href="https://agentmods.dev/commands/ffroliva/gflow-cli/issue-assessment"><img src="https://agentmods.dev/badge/commands/ffroliva/gflow-cli/issue-assessment/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/issue-assessment"><img src="https://agentmods.dev/badge/commands/ffroliva/gflow-cli/issue-assessment.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.00092 | $0.00375 |
| Opus 5.5 | $0.00037 | $0.00150 |
| Sonnet 5.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 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: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.
- 1mo 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 (337 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 375 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 commands, from other repositories
maintainer-review-error-handling
Review the PR for error-handling correctness — surfaced errors, no silent swallows, consistent error patterns (Pi-tuned).
lint
Check the project for naming, security and best-practice issues.
fix-issue
Diagnose and fix a reported bug, with the evidence bar the PR checklist expects.
review
Review the branch's changes against the CLAUDE.md PR checklist.
afr
Review feature - code review with fixes by a different agent (shortcut for feature-code-review).
hatch3r-codebase-map
Reverse-engineer a brownfield codebase into current-state module boundaries, integration-point inventory, tech-debt register, and dependency graph via static analysis.