agent-swarm-issue

agent-swarm-issue is a skill for Claude Code from proffesor-for-testing/agentic-qe. It costs 21 tokens per session (3,888 once invoked), scanned A, a copy of agent-swarm-issue, MIT.

A GitHub issue coordinator that turns issues into organized tasks for multiple AI agents. GitHub Issues are shared records used to describe bugs, requests, and other work.

In plain words
What is it for?
It is for reading, creating, updating, and commenting on GitHub issues while coordinating agent work and tracking progress.
Why use it?
It reduces manual task breakdown and keeps assignments, progress, and follow-up work connected to the original issue.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the TodoWrite tool; installed under .agents/ (shared by several agents); $skill-name invocation.

Part of the claude-flow plugin — 123 skills, 8 commands, 9 agents shipped together

Good fit It is for reading, creating, updating, and commenting on GitHub issues while coordinating agent work and tracking progress.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/proffesor-for-testing/agentic-qe/agent-swarm-issue
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.

Any agent
npx skills add proffesor-for-testing/agentic-qe --skill agent-swarm-issue
Clone the repo
git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe

Made for: Claude Code.

Or install claude-flow, the plugin that ships this one along with the rest of its 123 skills, 8 commands, 9 agents.

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 agent-swarm-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-swarm-issue/github.svg)](https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-swarm-issue)
Your own site
<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-swarm-issue"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-swarm-issue/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 agent-swarm-issue

Your own site · 80×15
<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-swarm-issue"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-swarm-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,888 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 100% copy Near-identical to another mod 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.03888
Opus 5.5 $0.00008 $0.01555
Sonnet 5.5 $0.00004 $0.00778
Haiku 4.5 $0.00002 $0.00389

Measured 1mo ago against content hash d19d573989da, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-swarm-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 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.

Origin

This is a copy

100% identical to agent-swarm-issue — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/ruflo/.agents/skills/agent-swarm-issue/SKILL.md · 578 lines

How it starts

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


name: swarm-issue description: GitHub issue-based swarm coordination agent that transforms issues into intelligent multi-agent tasks with automatic decomposition and progress tracking type: coordination color: "#FF6B35" tools:

  • mcp__github__get_issue
  • mcp__github__create_issue
  • mcp__github__update_issue
  • mcp__github__list_issues
  • mcp__github__create_issue_comment
  • mcp__claude-flow__swarm_init
  • mcp__claude-flow__agent_spawn
  • mcp__claude-flow__task_orchestrate
  • mcp__claude-flow__memory_usage
  • TodoWrite
  • TodoRead
  • Bash
  • Grep
  • Read
  • Write hooks: pre:
    • "Initialize swarm coordination system for GitHub issue management"
    • "Analyze issue context and determine optimal swarm topology"
    • "Store issue metadata in swarm memory for cross-agent access" post:
    • "Update issue with swarm progress and agent assignments"
    • "Create follow-up tasks based on swarm analysis results"
    • "Generate comprehensive swarm coordination report"

Swarm Issue - Issue-Based Swarm Coordination

Overview

Transform GitHub Issues into intelligent swarm tasks, enabling automatic task decomposition and agent coordination with advanced multi-agent orchestration.

Core Features

1. Issue-to-Swarm Conversion

# Create swarm from issue using gh CLI
# Get issue details
ISSUE_DATA=$(gh issue view 456 --json title,body,labels,assignees,comments)

# Create swarm from issue
npx ruv-swarm github issue-to-swarm 456 \
  --issue-data "$ISSUE_DATA" \
  --auto-decompose \
  --assign-agents

# Batch process multiple issues
ISSUES=$(gh issue list --label "swarm-ready" --json number,title,body,labels)
npx ruv-swarm github issues-batch \
  --issues "$ISSUES" \
  --parallel

# Update issues with swarm status
echo "$ISSUES" | jq -r '.[].number' | while read -r num; do
  gh issue edit $num --add-label "swarm-processing"
done

2. Issue Comment Commands

Execute swarm operations via issue comments:

<!-- In issue comment -->
$swarm analyze
$swarm decompose 5
$swarm assign @agent-coder
$swarm estimate
$swarm start

Read the full file on GitHub · 578 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. 1mo ago First seen · 578 lines · 21 tokens per session scan A d19d573989da

Subscribe to this mod's changes

agent-swarm-issue is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (514 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 3,888 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-swarm-issue, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens