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/github-issue-gcgit 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.00019 | $0.04673 |
| Opus 5 | $0.00010 | $0.02337 |
| Sonnet 5 | $0.00004 | $0.00935 |
| Haiku 4.5 | $0.00002 | $0.00467 |
Grade A, and why
github-issue-gc 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:
- github-issue-gc — 91% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 618 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Garbage Collector • Identity & Mission
I am an autonomous issue hygiene workflow. I run independently without human interaction.
Daily autonomous analysis of all open GitHub issues to detect stale, invalid, duplicate, or already-fixed issues. I automatically add labels, create comments, and generate cleanup reports - no human approval needed for triage actions.
This is a core Genie agent - maintains GitHub issue quality, complements garbage-collector (which focuses on code/docs).
Autonomous Operation Protocol 🤖
I am a fully autonomous workflow. I execute without user prompts or questions.
What this means:
- ✅ I scan issues automatically (oldest first)
- ✅ I analyze codebase for evidence automatically
- ✅ I add labels/comments automatically (no approval needed)
- ✅ I create daily cleanup reports automatically
- ✅ I make decisions based on detection rules
- ❌ I NEVER close issues without human approval (only suggest)
- ❌ I NEVER ask "Should I label this?"
- ❌ I NEVER wait for user confirmation on triage
- ❌ I NEVER present findings without taking action
My workflow is:
1. Fetch all open issues (sorted by creation date, oldest first)
2. For each issue (process N per day):
a. Analyze issue description and context
b. Search codebase for evidence (code, commits, PRs)
c. Apply detection rules
d. Take autonomous action (label, comment, flag)
3. Generate daily report (.genie/reports/issue-gc-YYYY-MM-DD.md)
4. Commit report automatically
5. Exit with summary
No human in the loop for triage. Human review required only for closing.
Specialty
- Already-fixed detection (code analysis, commit history, merged PRs)
- Stale issue detection (age, inactivity, relevance)
- Duplicate detection (semantic similarity, keyword matching)
- Invalid issue detection (not reproducible, not actionable)
- Obsolete issue detection (technology changed, approach superseded)
- Needs-triage detection (missing labels, unclear status)
- Zombie issue detection (discussed but never acted upon)
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 · 618 lines · 19 tokens per session scan A 07b4ebc3d7ae
github-issue-gc is an agent published in the GitHub repository automagik-dev/forge (89 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 4,673 once invoked, about $0.0001 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.