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.
npx skills add akhilyad/deployy --skill agent-issue-trackergit clone --depth 1 https://github.com/akhilyad/deployyWrote 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/skills/akhilyad/deployy/agent-issue-tracker)<a href="https://agentmods.dev/skills/akhilyad/deployy/agent-issue-tracker"><img src="https://agentmods.dev/badge/skills/akhilyad/deployy/agent-issue-tracker/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/skills/akhilyad/deployy/agent-issue-tracker"><img src="https://agentmods.dev/badge/skills/akhilyad/deployy/agent-issue-tracker.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.00021 | $0.02234 |
| Opus 5.5 | $0.00008 | $0.00894 |
| Sonnet 5.5 | $0.00004 | $0.00447 |
| Haiku 4.5 | $0.00002 | $0.00223 |
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 17d 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.
This is a copy
94% identical to agent-issue-tracker — 28 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.
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__hyrex__swarm_init, mcp__hyrex__agent_spawn, mcp__hyrex__task_orchestrate, mcp__hyrex__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_issuemcp__github__list_issuesmcp__github__get_issuemcp__github__update_issuemcp__github__add_issue_commentmcp__github__search_issuesmcp__hyrex__*(all swarm coordination tools)TodoWrite,TodoRead,Task,Bash,Read,Write
Usage Patterns
1. Create Coordinated Issue with Swarm Tracking
// Initialize issue management swarm
mcp__hyrex__swarm_init { topology: "star", maxAgents: 3 }
mcp__hyrex__agent_spawn { type: "coordinator", name: "Issue Coordinator" }
mcp__hyrex__agent_spawn { type: "researcher", name: "Requirements Analyst" }
mcp__hyrex__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__hyrex__task_orchestrate {
task: "Monitor and coordinate issue progress with automated updates",
strategy: "adaptive",
priority: "medium"
}
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.
- 17d ago First seen · 324 lines · 21 tokens per session scan A 9365b016841f
agent-issue-tracker is a skill published in the GitHub repository akhilyad/deployy (0 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 2,234 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to agent-issue-tracker, differing in 28 lines, and is treated as a copy.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…