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.
git clone --depth 1 https://github.com/monoes/monomindWrote 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/monoes/monomind/issue-tracker)<a href="https://agentmods.dev/commands/monoes/monomind/issue-tracker"><img src="https://agentmods.dev/badge/commands/monoes/monomind/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/commands/monoes/monomind/issue-tracker"><img src="https://agentmods.dev/badge/commands/monoes/monomind/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.00030 | $0.01970 |
| Opus 5.5 | $0.00012 | $0.00788 |
| Sonnet 5.5 | $0.00006 | $0.00394 |
| Haiku 4.5 | $0.00003 | $0.00197 |
Grade A, and why
github: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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Tracker
Purpose
Intelligent issue management and project coordination with monomind 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__monomind__*(all swarm coordination tools)TodoWrite,TodoRead,Task,Bash,Read,Write
Usage Patterns
1. Create Coordinated Issue with Swarm Tracking
// Spawn issue management agents
mcp__monomind__agent_spawn { type: "coordinator", name: "Issue Coordinator" }
mcp__monomind__agent_spawn { type: "researcher", name: "Requirements Analyst" }
mcp__monomind__agent_spawn { type: "coder", name: "Implementation Planner" }
// Create comprehensive issue
mcp__github__create_issue {
owner: ":owner",
repo: ":repo",
title: "Integration Review: comprehensive package 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: [":assignee"]
}
// Set up automated tracking
mcp__monomind__task_create {
description: "Monitor and coordinate issue progress with automated updates",
agents: ["coordinator", "researcher", "coder"],
strategy: "parallel"
}
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.
- yesterday First seen · 293 lines · 30 tokens per session scan A 2ca6e7306d78
github:issue-tracker is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 30 tokens to every session and 1,970 once invoked, about $0.0001 per session on Opus 5.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-10-26.
Other commands, from other repositories
multi-repo-swarm
Coordinate AI swarms across multiple repositories, enabling organization-wide automation and intelligent cross-project collaboration.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
auto-agent
Automatically spawn and manage agents based on task requirements.
jira
Retrieve a Jira ticket, analyze requirements, update status, or add comments. Uses the jira-integration skill and MCP or REST API.
bienvenida
Grupo: Rutina del día a día En una frase: Primera vez post-clone — checklist + mensaje de bienvenida con commands recomendados (incluye /setup si falta estructura). Cuándo: Justo después de clonar o abrir el DT por primera vez; la IA también puede mostrarlo sin invocación si no hay sesión local. Quién: Cualquier…
morning
The coffee report — cross-project map deltas, arrives on its own (scheduled).