opengrok-go-mcp: Command for Claude Code

.opencode/commands/speckit.taskstoissues.md

speckit.taskstoissues is a command for Claude Code, OpenCode from rokasklive/opengrok-go-mcp. It costs 21 tokens per session (916 once invoked), scanned A, original, Apache-2.0.

A command that converts an existing feature task list into GitHub issues arranged by dependency. GitHub issues are trackable work items for a repository.

In plain words
What is it for?
Use it when tasks are already defined and the team needs actionable GitHub issues for implementation.
Why use it?
It avoids manually rewriting planned tasks as issues and preserves the order in which the work should be done.

Command for Claude CodeOpenCode

Written for Claude Code and OpenCode: $ARGUMENTS substitution, but also installed under .opencode/. Also seen: Copilot chat-mode frontmatter (tools: vscode/*).

This is rokasklive/opengrok-go-mcp's own configuration. It tells Claude Code and OpenCode how to work on opengrok-go-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything opengrok-go-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to rokasklive/opengrok-go-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rokasklive/opengrok-go-mcp/main/.opencode/commands/speckit.taskstoissues.md
Clone the repo
git clone --depth 1 https://github.com/rokasklive/opengrok-go-mcp

Made for: Claude Code, OpenCode.

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 speckit.taskstoissues

README.md
[![agentmods](https://agentmods.dev/badge/commands/rokasklive/opengrok-go-mcp/speckit.taskstoissues/github.svg)](https://agentmods.dev/commands/rokasklive/opengrok-go-mcp/speckit.taskstoissues)
Your own site
<a href="https://agentmods.dev/commands/rokasklive/opengrok-go-mcp/speckit.taskstoissues"><img src="https://agentmods.dev/badge/commands/rokasklive/opengrok-go-mcp/speckit.taskstoissues/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.

agentmods 80×15 button for speckit.taskstoissues

Your own site · 80×15
<a href="https://agentmods.dev/commands/rokasklive/opengrok-go-mcp/speckit.taskstoissues"><img src="https://agentmods.dev/badge/commands/rokasklive/opengrok-go-mcp/speckit.taskstoissues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 916 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00021 $0.00916
Opus 5 $0.00010 $0.00458
Sonnet 5 $0.00004 $0.00183
Haiku 4.5 $0.00002 $0.00092

Measured 9d ago against content hash e84794f7a839, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

speckit.taskstoissues 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 9d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.opencode/commands/speckit.taskstoissues.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Pre-Execution Checks

Check for extension hooks (before tasks-to-issues conversion):

  • Check if .specify/extensions.yml exists in the project root.
  • If it exists, read it and look for entries under the hooks.before_taskstoissues key
  • If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
  • Filter out hooks where enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
  • For each remaining hook, do not attempt to interpret or evaluate hook condition expressions:
    • If the hook has no condition field, or it is null/empty, treat the hook as executable
    • If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementation
  • For each executable hook, output the following based on its optional flag:
    • Optional hook (optional: true):
      ## Extension Hooks
      
      **Optional Pre-Hook**: {extension}
      Command: `/{command}`
      Description: {description}
      
      Prompt: {prompt}
      To execute: `/{command}`
      
    • Mandatory hook (optional: false):
      ## Extension Hooks
      
      **Automatic Pre-Hook**: {extension}
      Executing: `/{command}`
      EXECUTE_COMMAND: {command}
      
      Wait for the result of the hook command before proceeding to the Outline.
      
  • If no hooks are registered or .specify/extensions.yml does not exist, skip silently

Outline

  1. Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").
  2. From the executed script, extract the path to tasks.
  3. Get the Git remote by running:
git config --get remote.origin.url

Read the full file on GitHub · 97 lines

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. 9d ago First seen · 97 lines · 21 tokens per session scan A e84794f7a839

Subscribe to this mod's changes

speckit.taskstoissues is a command published in the GitHub repository rokasklive/opengrok-go-mcp (7 stars, last pushed 23d ago), licensed Apache-2.0. It adds 21 tokens to every session and 916 once invoked, about $0.0001 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-31.