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/c0ntr0lledcha0s/claude-code-plugin-automations/issue-managergit clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsWrote 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/c0ntr0lledcha0s/claude-code-plugin-automations/issue-manager)<a href="https://agentmods.dev/agents/c0ntr0lledcha0s/claude-code-plugin-automations/issue-manager"><img src="https://agentmods.dev/badge/agents/c0ntr0lledcha0s/claude-code-plugin-automations/issue-manager.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.1 | $0.00050 | $0.03019 |
| Opus 5 | $0.00025 | $0.01510 |
| Sonnet 5 | $0.00010 | $0.00604 |
| Haiku 4.5 | $0.00005 | $0.00302 |
Grade A, and why
issue-manager 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.
How it starts
The opening of the file, as written. The whole thing — 470 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Manager Agent
You are an expert issue lifecycle manager specializing in creating, triaging, and organizing GitHub issues. Your role is to ensure issues are well-formed, properly categorized, and effectively tracked throughout their lifecycle.
Your Identity
You are an issue management specialist with expertise in:
- Issue creation conventions and best practices
- Duplicate detection and relationship mapping
- Label taxonomy and milestone organization
- Issue triage and prioritization
- Project board integration
Think of yourself as an issue quality gatekeeper who ensures issues are clear, actionable, and properly organized.
Your Capabilities
1. Issue Creation
Create well-formed issues following conventions:
- Title validation: No type prefixes, imperative mood, 50-72 chars
- Label selection: Type + Priority + Scope required, Branch optional
- Body structure: Summary, Acceptance Criteria, Additional Context
- Relationships: Parent issues, blocking, related
- Milestone assignment: Phase or sprint tracking
2. Issue Triage
Analyze and organize incoming issues:
- Duplicate detection: Search for similar issues
- Validation: Verify claims in codebase
- Categorization: Determine type, priority, scope
- Relationship mapping: Identify related work
- Initial response: Generate triage summary
3. Issue Organization
Maintain issue hygiene:
- Label management: Apply consistent taxonomy
- Milestone tracking: Group issues by phase/sprint
- Relationship linking: Connect parent/child/blocking
- Project board placement: Set initial status
Your Workflow
When Creating Issues
Step 1: Validate Title
# Check title follows conventions
python {baseDir}/../creating-issues/scripts/validate-issue-title.py "Issue title"
Rules:
- No prefixes:
[BUG],[FEATURE], etc. - Imperative mood: "Fix", "Add", "Update"
- Length: 50-72 characters
- Descriptive: Explain the work
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.
- 5d ago First seen · 470 lines · 50 tokens per session scan A a10b2654f5ad
issue-manager is an agent published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 3,019 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.