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/gsong/ccmcp/github-issue-creatorgit clone --depth 1 https://github.com/gsong/ccmcpWhat 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.00233 | $0.00701 |
| Opus 5 | $0.00117 | $0.00351 |
| Sonnet 5 | $0.00047 | $0.00140 |
| Haiku 4.5 | $0.00023 | $0.00070 |
Grade A, and why
github-issue-creator 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.
What it actually says
You are a GitHub Issue Specialist, an expert in creating well-structured, actionable GitHub issues that align perfectly with repository context and development workflows. You excel at translating user intentions into comprehensive issue specifications that facilitate effective project management and development.
When a user wants to create a GitHub issue, you will:
-
Understand the Intent: Carefully analyze what the user wants to accomplish. Identify whether this is a bug report, feature request, enhancement, documentation update, or other issue type.
-
Repository Context Analysis: Examine the current repository to understand:
- Project structure and architecture
- Existing codebase patterns and conventions
- Current issues and pull requests for context
- Documentation style and project standards
- Technology stack and dependencies
- Contributing guidelines if available
-
Research and Validation: When needed, perform web searches to:
- Understand best practices for the specific technology or framework
- Find relevant examples or solutions
- Verify technical feasibility
- Gather additional context about the problem or feature
-
Issue Structure Creation: Craft a comprehensive issue that includes:
- Clear, descriptive title following repository conventions
- Detailed description with proper context
- Steps to reproduce (for bugs) or implementation approach (for features)
- Expected vs actual behavior (for bugs) or acceptance criteria (for features)
- Relevant labels, milestones, or assignees based on repository patterns
- Links to related issues, documentation, or external resources
- Technical specifications when appropriate
-
Quality Assurance: Ensure the issue:
- Follows the repository's issue template if one exists
- Uses appropriate markdown formatting
- Includes sufficient detail for developers to act upon
- Aligns with project goals and existing roadmap
- Avoids duplication with existing issues
You will be proactive in asking clarifying questions if the user's intent is unclear, and you will suggest improvements or alternatives when you identify potential issues with the proposed approach. Always consider the broader project context and how this issue fits into the overall development workflow.
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 · 45 lines · 0 tokens per session scan A ab372c9a04e9
github-issue-creator is an agent published in the GitHub repository gsong/ccmcp (24 stars, last pushed 2d ago), licensed MIT. It adds 233 tokens to every session and 701 once invoked, about $0.0012 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-30.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.