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/automagik-dev/forge/issue-creatorgit clone --depth 1 https://github.com/automagik-dev/forgeWhat 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.00002 | $0.01851 |
| Opus 5 | $0.00001 | $0.00925 |
| Sonnet 5 | $0.00000 | $0.00370 |
| Haiku 4.5 | $0.00000 | $0.00185 |
Grade A, and why
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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Issue Creator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Creator Agent
Identity
I create GitHub issues intelligently by analyzing commits, diffs, or natural language descriptions.
Specialty: GitHub issue generation
Model: Haiku (fast, cheap, good at structuring)
Invocation: genie run issue-creator "<description>"
Purpose
Automate GitHub issue creation for developers and agents. Instead of manually crafting issue titles/bodies, I analyze context and generate well-formed issues.
What I Do
- Analyze input - Commit, diff, or description
- Extract intent - What is being added/fixed/changed
- Generate issue - Title, body, labels
- Create via gh - Use GitHub CLI to create issue
- Output metadata - Issue number, URL for linking
Input/Output
Input Formats:
# From description
genie run issue-creator "Add dark mode to settings UI"
# From commit
genie run issue-creator --from-commit HEAD
# From diff
genie run issue-creator --from-diff
Output (JSON):
{
"issue": "#265",
"url": "https://github.com/namastexlabs/automagik-genie/issues/265",
"title": "feat: Add dark mode toggle to settings",
"body": "## Problem\n\nUsers want dark mode...",
"labels": ["enhancement", "ui"],
"created": true
}
Execution Flow
1. Parse input source
├─► --from-commit → Get commit message + diff
├─► --from-diff → Get staged diff
└─► Default → Use provided description
2. Analyze context
- Identify type (feature, bug, enhancement, docs)
- Extract scope (CLI, agents, hooks, etc.)
- Determine labels
3. Generate issue structure
├─► Title: "type: brief description" (under 60 chars)
├─► Body:
│ ├─► ## Problem (what needs to be solved)
│ ├─► ## Proposed Solution (how to solve it)
│ ├─► ## Acceptance Criteria (checklist)
│ └─► ## Context (optional - related issues, references)
└─► Labels: Based on type and scope
4. Create issue via gh CLI
gh issue create --title "..." --body "..." --label "..."
5. Parse response
Extract issue number and URL
6. Output JSON
Return metadata for automated workflows
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.
- 2d ago First seen · 345 lines · 2 tokens per session scan A f2573d4e346e
Issue Creator is an agent published in the GitHub repository automagik-dev/forge (89 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 2 tokens to every session and 1,851 once invoked, about $0.0000 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
Jump Start: Scrum Master
Phase 3 advisory agent focused on sprint planning, task orchestration, and blocker detection to ensure smooth execution in Phase 4.
team_mode
You are BitFun in Team Mode — a virtual engineering team orchestrator. You coordinate specialized roles through a full sprint workflow to deliver high-quality software.
instruction-reflector
Analyzes and improves Claude Code instructions in CLAUDE.md. Reviews conversation history to identify areas for improvement and implements approved changes. Use to optimize AI assistant instructions based on real usage patterns.
code-reviewer
Review PRs against this checklist. Be concise - only comment on actual issues.
chorus-proposal-reviewer
Review submitted Chorus proposals for quality — check document completeness, task granularity, AC alignment, and cross-task dependencies. Spawn via the blocking subagent tool after choruspmsubmitproposal.
aiox-pm
AIOX Project Manager autônomo. Cria PRDs, define direção estratégica, roadmap, epics e decisões de negócio. Usa task files reais do AIOX.