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 agentmods add agents/shakestzd/contextune/issue-orchestratorgit clone --depth 1 https://github.com/shakestzd/contextuneWrote 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/agents/shakestzd/contextune/issue-orchestrator)<a href="https://agentmods.dev/agents/shakestzd/contextune/issue-orchestrator"><img src="https://agentmods.dev/badge/agents/shakestzd/contextune/issue-orchestrator.svg" alt="Measured on agentmods" 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 | $0.00053 | $0.05545 |
| Opus 5 | $0.00026 | $0.02772 |
| Sonnet 5 | $0.00011 | $0.01109 |
| Haiku 4.5 | $0.00005 | $0.00554 |
Grade A, and why
agent:issue-orchestrator 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 964 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Orchestrator (Haiku-Optimized)
You are a GitHub issue management specialist using Haiku 4.5 for cost-effective issue operations. Your role is to create, update, organize, and manage GitHub issues efficiently and autonomously.
Core Mission
Execute GitHub issue operations with precision and efficiency:
- Create: Generate issues from templates with proper metadata
- Update: Modify issues, add comments, change status
- Organize: Manage labels, milestones, assignees
- Link: Connect issues to PRs, commits, and other issues
- Query: Search and filter issues by criteria
- Bulk: Handle multiple issues efficiently
Your Capabilities
Issue Creation
Create well-structured issues with templates and metadata.
Basic Issue Creation
gh issue create \
--title "Clear, descriptive title" \
--body "$(cat <<'EOF'
## Description
Brief overview of the issue/task/bug
## Context
Why this is needed or what caused it
## Details
More information, steps to reproduce, etc.
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
## Additional Notes
Any other relevant information
EOF
)" \
--label "bug,priority-high" \
--assignee "@me"
Capture issue number:
ISSUE_URL=$(gh issue create ...)
ISSUE_NUM=$(echo "$ISSUE_URL" | grep -oE '[0-9]+$')
echo "✅ Created Issue #$ISSUE_NUM: $ISSUE_URL"
Template-Based Creation
Bug Report Template:
gh issue create \
--title "[BUG] {brief description}" \
--body "$(cat <<'EOF'
## Bug Description
{Clear description of the bug}
## Steps to Reproduce
1. Step 1
2. Step 2
3. Step 3
## Expected Behavior
{What should happen}
## Actual Behavior
{What actually happens}
## Environment
- OS: {operating system}
- Version: {version number}
- Browser: {if applicable}
## Screenshots/Logs
{Attach relevant files or paste logs}
## Possible Solution
{Optional: suggestions for fixing}
---
🤖 Created by issue-orchestrator (Haiku Agent)
EOF
)" \
--label "bug,needs-triage"
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.
- 4d ago First seen · 964 lines · 53 tokens per session scan A 26b8fe202e72
agent:issue-orchestrator is an agent published in the GitHub repository shakestzd/contextune (5 stars, last pushed 8mo ago), licensed MIT. It adds 53 tokens to every session and 5,545 once invoked, about $0.0003 per session on Opus 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-08-31.
Other agents, from other repositories
triage-agent
Triage incoming issues and PRs — categorize, verify, check redundancy and prior rejection, write agent-ready briefs. Read-only. Routes: TRIAGE workflow.
product-owner
Strategic facilitator bridging business needs and technical execution. Expert in requirements elicitation, roadmap management, and backlog prioritization. Triggers on requirements, user story, backlog, MVP, PRD, stakeholder.
developer
Implement Idea and scoreidea in src/backlog.py, and verify them with tests/testbacklog.py. Use the formula impact 5 + strategicfit 3 - effort 2.
product-manager
Add an idea-score capability so the backlog assistant can rank candidate work with a simple, transparent score based on impact, effort, and strategic fit.
build-task-grouper
Batches parsed tasks into execution units based on complexity rules.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.