agent-issue-tracker

agent-issue-tracker is a skill for Claude Code from Soulcynics404/AgentForge. It costs 21 tokens per session (2,251 once invoked), scanned A, a copy of agent-issue-tracker, MIT.

A coding-agent skill for managing project issues and coordinating work across repositories. Issues are tracked work items such as bugs, feature requests, and tasks.

In plain words
What is it for?
Creating and organizing GitHub issues, tracking progress, coordinating milestones, and synchronizing issues across repositories.
Why use it?
It helps organize issue creation, labels, milestones, progress, and coordination when work spans teams or repositories.

Skill for Claude Code

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

Part of the claude-flow plugin — 134 skills, 52 commands, 11 agents, 4 hooks, 1 MCP server shipped together

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 skills/soulcynics404/agentforge/agent-issue-tracker
Any agent
npx skills add Soulcynics404/AgentForge --skill agent-issue-tracker
Clone the repo
git clone --depth 1 https://github.com/Soulcynics404/AgentForge

Made for: Claude Code.

Or install claude-flow, the plugin that ships this one along with the rest of its 134 skills, 52 commands, 11 agents, 4 hooks, 1 MCP server.

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-issue-tracker

README.md
[![agentmods](https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-issue-tracker.svg)](https://agentmods.dev/skills/soulcynics404/agentforge/agent-issue-tracker)
Your own site
<a href="https://agentmods.dev/skills/soulcynics404/agentforge/agent-issue-tracker"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-issue-tracker.svg" alt="Measured on agentmods" 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 2,251 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.02251
Opus 5 $0.00010 $0.01125
Sonnet 5 $0.00004 $0.00450
Haiku 4.5 $0.00002 $0.00225

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

Security

Grade A, and why

agent-issue-tracker 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 5d 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-issue-tracker — 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/agent-issue-tracker/SKILL.md · 324 lines

How it starts

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


name: issue-tracker description: Intelligent issue management and project coordination with automated tracking, progress monitoring, and team coordination tools: mcp__claude-flow__swarm_init, mcp__claude-flow__agent_spawn, mcp__claude-flow__task_orchestrate, mcp__claude-flow__memory_usage, Bash, TodoWrite, Read, Write color: green type: development capabilities:

  • Automated issue creation with smart templates
  • Progress tracking with swarm coordination
  • Multi-agent collaboration on complex issues
  • Project milestone coordination
  • Cross-repository issue synchronization
  • Intelligent labeling and organization priority: medium hooks: pre: | echo "Starting issue-tracker..." echo "Initializing issue management swarm" gh auth status || (echo "GitHub CLI not authenticated" && exit 1) echo "Setting up issue coordination environment" post: | echo "Completed issue-tracker" echo "Issues created and coordinated" echo "Progress tracking initialized" echo "Swarm memory updated with issue state"

GitHub Issue Tracker

Purpose

Intelligent issue management and project coordination with ruv-swarm integration for automated tracking, progress monitoring, and team coordination.

Capabilities

  • Automated issue creation with smart templates and labeling
  • Progress tracking with swarm-coordinated updates
  • Multi-agent collaboration on complex issues
  • Project milestone coordination with integrated workflows
  • Cross-repository issue synchronization for monorepo management

Tools Available

  • mcp__github__create_issue
  • mcp__github__list_issues
  • mcp__github__get_issue
  • mcp__github__update_issue
  • mcp__github__add_issue_comment
  • mcp__github__search_issues
  • mcp__claude-flow__* (all swarm coordination tools)
  • TodoWrite, TodoRead, Task, Bash, Read, Write

Usage Patterns

1. Create Coordinated Issue with Swarm Tracking

// Initialize issue management swarm
mcp__claude-flow__swarm_init { topology: "star", maxAgents: 3 }
mcp__claude-flow__agent_spawn { type: "coordinator", name: "Issue Coordinator" }
mcp__claude-flow__agent_spawn { type: "researcher", name: "Requirements Analyst" }
mcp__claude-flow__agent_spawn { type: "coder", name: "Implementation Planner" }

// Create comprehensive issue
mcp__github__create_issue {
  owner: "ruvnet",
  repo: "ruv-FANN",
  title: "Integration Review: claude-code-flow and ruv-swarm complete integration",
  body: `## 🔄 Integration Review
  
  ### Overview
  Comprehensive review and integration between packages.
  
  ### Objectives
  - [ ] Verify dependencies and imports
  - [ ] Ensure MCP tools integration
  - [ ] Check hook system integration
  - [ ] Validate memory systems alignment
  
  ### Swarm Coordination
  This issue will be managed by coordinated swarm agents for optimal progress tracking.`,
  labels: ["integration", "review", "enhancement"],
  assignees: ["ruvnet"]
}

// Set up automated tracking
mcp__claude-flow__task_orchestrate {
  task: "Monitor and coordinate issue progress with automated updates",
  strategy: "adaptive",
  priority: "medium"
}

Read the full file on GitHub · 324 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. 5d ago First seen · 324 lines · 21 tokens per session scan A 057b4ae6d10a

Subscribe to this mod's changes

agent-issue-tracker is a skill published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 12d ago), licensed MIT. It adds 21 tokens to every session and 2,251 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-issue-tracker, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

building-pydantic-ai-agents

Build AI agents with Pydantic AI — tools, capabilities (including on-demand loading), structured output, streaming, testing, and multi-agent patterns. Use when the user mentions Pydantic AI, imports pydanticai, or asks to build an AI agent, add tools/capabilities, defer capability loading, stream output, define agents…

pydantic/pydantic-ai · 85 tokens

complete-partial-pr

Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.

pydantic/pydantic-ai · 55 tokens

testing-skill

Record, rewrite, and debug VCR cassettes for HTTP recordings. Use when running tests with --record-mode, verifying cassette playback, or inspecting request/response bodies in YAML cassettes.

pydantic/pydantic-ai · 44 tokens

adding-a-provider-api-feature

Add a new provider API capability (prompt caching, strict/structured tool calling, thinking/reasoning effort, service tier, safety settings, logprobs, etc.) to Pydantic AI. Use when wiring a provider feature through the library — it enforces reasoning from the existing cross-provider abstraction before designing…

pydantic/pydantic-ai · 97 tokens

migrating-langchain-to-pydantic-ai

Migrate Python LangChain or LangGraph applications to Pydantic AI. Use for LangChain agents, chains, LCEL, or direct LangGraph graphs, persistence, interrupts, and streaming. Do not use for migrations centered on createdeepagent or Deep Agents harness features.

pydantic/pydantic-ai · 69 tokens

address-feedback

Find and address unresolved PR review comments for the current branch, then continue the canonical push, reply, reaction, and resolution workflow.

pydantic/pydantic-ai · 29 tokens