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.
git clone --depth 1 https://github.com/automagik-dev/forgeWrote 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/automagik-dev/forge/github-issue-gc)<a href="https://agentmods.dev/agents/automagik-dev/forge/github-issue-gc"><img src="https://agentmods.dev/badge/agents/automagik-dev/forge/github-issue-gc/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/automagik-dev/forge/github-issue-gc"><img src="https://agentmods.dev/badge/agents/automagik-dev/forge/github-issue-gc.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.04673 |
| Opus 5.5 | $0.00008 | $0.01869 |
| Sonnet 5.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 1mo 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
2 near-identical copies found in the catalogue:
- github-issue-gc — 91% identical, 3 lines differ
- 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.
- 1mo 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 (92 stars, last pushed 10mo 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.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
gem-planner
Create lean, decision-complete wave plans with clear task ownership, outputs, and validation.
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.
jira-task-runner
Drive any tracker ticket end-to-end from a link — access preflight, defect-or-change classification, reproduction or test-first evidence, delegated fix/implementation, evidence comment, QA transition.
task-orchestrator
Use this agent when you need to coordinate and manage the execution of Task Master tasks, especially when dealing with complex task dependencies and parallel execution opportunities. This agent should be invoked at the beginning of a work session to analyze the task queue, identify parallelizable work, and orchestrate…
phase-executor
Executes plans with deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator.
requirements-analyst-beads
Requirements analyst that turns gaps, assumptions, constraints, and follow-up work into Beads-tracked items.