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.
curl -O https://raw.githubusercontent.com/rokasklive/opengrok-go-mcp/main/.github/prompts/speckit.taskstoissues.prompt.mdgit clone --depth 1 https://github.com/rokasklive/opengrok-go-mcpWrote 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/rokasklive/opengrok-go-mcp/speckit.taskstoissues)<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.
<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>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.00011 |
| Opus 5.5 | $0.00000 | $0.00004 |
| Sonnet 5.5 | $0.00000 | $0.00002 |
| Haiku 4.5 | $0.00000 | $0.00001 |
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 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- speckit-taskstoissues — 92% identical, 116 lines differ
- speckit.taskstoissues — 89% identical, 95 lines differ
The source is not reproduced here
Licensed Apache-2.0
The repository is licensed Apache-2.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 Changed · -93 lines · -21 tokens per session 2f9636d4f312
- 1mo ago First seen · 97 lines · 21 tokens per session scan A e84794f7a839
speckit.taskstoissues is a command published in the GitHub repository rokasklive/opengrok-go-mcp (10 stars, last pushed 13d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 11 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.
Other commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
standup
Review my git commits from the past workday and generate a standup summary.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.