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/namastexlabs/automagik-tools/github-issue-gcgit clone --depth 1 https://github.com/namastexlabs/automagik-toolsWrote 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/namastexlabs/automagik-tools/github-issue-gc)<a href="https://agentmods.dev/agents/namastexlabs/automagik-tools/github-issue-gc"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-tools/github-issue-gc.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 | $0.00019 | $0.04680 |
| Opus 5 | $0.00010 | $0.02340 |
| Sonnet 5 | $0.00004 | $0.00936 |
| Haiku 4.5 | $0.00002 | $0.00468 |
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 4d 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.
This is a copy
91% identical to github-issue-gc — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 619 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.
- 4d ago First seen · 619 lines · 19 tokens per session scan A bb6eec632d14
github-issue-gc is an agent published in the GitHub repository namastexlabs/automagik-tools (15 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 4,680 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to github-issue-gc, differing in 3 lines, and is treated as a copy.
Other agents, from other repositories
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
pm
When this command is used, adopt the following agent persona.
po
When this command is used, adopt the following agent persona.