Borrowing it
Nothing to install: this file belongs to Kuadrant/mcp-gateway. 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/Kuadrant/mcp-gateway/main/.claude/commands/what-next.mdgit clone --depth 1 https://github.com/Kuadrant/mcp-gatewayWrote 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/kuadrant/mcp-gateway/what-next)<a href="https://agentmods.dev/commands/kuadrant/mcp-gateway/what-next"><img src="https://agentmods.dev/badge/commands/kuadrant/mcp-gateway/what-next.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.1 | $0.00000 | $0.00937 |
| Opus 5 | $0.00000 | $0.00468 |
| Sonnet 5 | $0.00000 | $0.00187 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
what-next 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 8d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What to Work on Next
Help the user identify what to focus on next based on the project's contribution process.
Contribution Process Reference
@CONTRIBUTING.md
Instructions
Follow these steps to gather information and present suggestions:
Step 1: Get GitHub username
Run gh api user --jq '.login' to get the current user's GitHub username.
Step 2: Check for PRs needing review
Run gh pr list --state open --json number,title,author,isDraft,reviewRequests,reviews,assignees,updatedAt,url to get all open PRs.
Filter the results:
- Exclude drafts unless the current user is an assignee AND there are comments in the last 48 hours
- Exclude PRs authored by the current user (you review others' work, not your own)
- Exclude PRs that are sufficiently reviewed: A PR is "sufficiently reviewed" if it has at least one APPROVED review, OR has 2+ reviews submitted in the last 24 hours
- Prioritize PRs where the current user is explicitly requested as a reviewer
Step 3: Check for the current user's PRs
From the same PR data, identify:
Assigned PRs with activity: PRs where current user is an assignee with recent comments (check with gh pr view <number> --json comments if needed). These may need attention even if drafts.
Your open PRs (non-draft): PRs authored by the current user that are not drafts. Note their review status:
- Has approval and no blocking reviews = ready to merge
- Has CHANGES_REQUESTED = needs your attention
- Waiting for review = note who's been requested
Your drafts: Draft PRs authored by the current user. Note how recently they were updated.
Step 4: Find upcoming milestone and priority issues
Run gh api repos/:owner/:repo/milestones --jq '[.[] | select(.state == "open") | select(.due_on)] | sort_by(.due_on) | .[0] | {number, title, due_on}' to find the next milestone with a due date (:owner/:repo is auto-substituted by gh CLI).
Then fetch issues for that milestone:
gh issue list --milestone "<milestone_title>" --state open --json number,title,labels,assignees,url
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.
- 8d ago First seen · 91 lines · 0 tokens per session scan A ab1539fe0e5a
what-next is a command published in the GitHub repository Kuadrant/mcp-gateway (98 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 937 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.