next-issue

next-issue is a command for Claude Code from carlwestman/borsdata-mcp-server. It costs 0 tokens per session (451 once invoked), scanned A, original, MIT.

A command for taking the highest-priority ready issue from a GitHub Project board and starting work on it. It moves the issue to In Progress, creates a branch, and records the start.

In plain words
What is it for?
Use it to claim the next ready GitHub issue, read its comments, create an issue-named branch, and begin implementation.
Why use it?
It turns issue selection and setup into a repeatable process, so work begins with the project board and issue history aligned.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/carlwestman/borsdata-mcp-server/next-issue
Clone the repo
git clone --depth 1 https://github.com/carlwestman/borsdata-mcp-server

Made for: Claude Code.

Wrote 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.

agentmods badge for next-issue

README.md
[![agentmods](https://agentmods.dev/badge/commands/carlwestman/borsdata-mcp-server/next-issue.svg)](https://agentmods.dev/commands/carlwestman/borsdata-mcp-server/next-issue)
Your own site
<a href="https://agentmods.dev/commands/carlwestman/borsdata-mcp-server/next-issue"><img src="https://agentmods.dev/badge/commands/carlwestman/borsdata-mcp-server/next-issue.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 451 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00451
Opus 5 $0.00000 $0.00226
Sonnet 5 $0.00000 $0.00090
Haiku 4.5 $0.00000 $0.00045

Measured 4d ago against content hash c9dab260f01c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

next-issue 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.

.claude/commands/next-issue.md · 52 lines

What it actually says

/next-issue — Pick up the next issue from the project board

You are picking up the next prioritised issue from the GitHub Project board.

Steps

  1. Get the next issue by running:

    ./scripts/gh-project.sh next
    

    This returns the top item in the "Ready" column (highest priority).

  2. If no items are in Ready, inform me and stop.

  3. Read the full issue including all comments for additional context:

    gh issue view <NUMBER> --repo $GH_PROJECT_OWNER/$GH_PROJECT_REPO --comments
    
  4. Move the issue to In Progress:

    ./scripts/gh-project.sh move <NUMBER> "In Progress"
    
  5. Create a working branch:

    git checkout -b issue-<NUMBER>-<short-slug> main
    

    Use a short kebab-case slug derived from the issue title.

  6. Add a progress header to the issue description so the team can see work has started:

    gh issue edit <NUMBER> --body "$(gh issue view <NUMBER> --json body -q .body)
    
    ---
    ## 🔧 Implementation Progress
    - ⏳ Started: $(date -u +%Y-%m-%dT%H:%M:%SZ)
    - Branch: \`issue-<NUMBER>-<slug>\`
    - Status: **In Progress**
    "
    
  7. Start implementing. Read any referenced files, specs, or docs mentioned in the issue. Follow the project's existing patterns and conventions. Refer to /docs and CLAUDE.md for project rules.

  8. Update the issue description periodically as you complete meaningful steps — append bullet points under the Implementation Progress section describing what was done.

Rules

  • Never force-push to main.
  • Always work on a feature branch.
  • Run existing tests before considering the work complete.
  • If the issue is unclear or blocked, add a comment to the issue asking for clarification and let me know.
Changes

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.

  1. 4d ago First seen · 52 lines · 0 tokens per session scan A c9dab260f01c

Subscribe to this mod's changes

next-issue is a command published in the GitHub repository carlwestman/borsdata-mcp-server (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 451 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-31.