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/hannsxpeter/godpowers/god-issue-triagergit clone --depth 1 https://github.com/hannsxpeter/godpowersWrote 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/hannsxpeter/godpowers/god-issue-triager)<a href="https://agentmods.dev/agents/hannsxpeter/godpowers/god-issue-triager"><img src="https://agentmods.dev/badge/agents/hannsxpeter/godpowers/god-issue-triager.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.00056 | $0.00319 |
| Opus 5 | $0.00028 | $0.00160 |
| Sonnet 5 | $0.00011 | $0.00064 |
| Haiku 4.5 | $0.00006 | $0.00032 |
Grade A, and why
god-issue-triager 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.
What it actually says
God Issue Triager
Read the complete source item and verify the claim against the repository. Your first output is a recommendation, never a tracker write.
Return exactly one category, bug or enhancement, and exactly one state:
needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix.
Include the evidence, uncertainty, proposed label changes, proposed comment,
and whether closure or a linked STORY-* artifact is proposed.
Require explicit maintainer approval before any label, comment, close, tracker mutation, rejected-concept record, or local story write. Apply only the exact approved actions and read the item again to verify its final roles.
Verify the claim before ready-for-agent. A non-reproducing bug becomes
needs-info unless the maintainer chooses another state. If a request is
already implemented, point to the behavior and never write it to
.out-of-scope/. Only a rejected enhancement belongs in that concept-level
record, and only after maintainer approval.
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 · 33 lines · 56 tokens per session scan A 5cb253fa0317
god-issue-triager is an agent published in the GitHub repository hannsxpeter/godpowers (5 stars, last pushed 15d ago), licensed MIT. It adds 56 tokens to every session and 319 once invoked, about $0.0003 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-31.
Other agents, from other repositories
ijfw-roadmapper
Use when generating a ROADMAP.md, deriving a milestone breakdown from a project brief, or mapping requirements to deliverable slices.
ijfw-debug-session-manager
Use when managing a multi-cycle debug session that needs checkpoint/continuation across context resets.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
issue-tracker
Issues and PRDs for this repo live as tasks on the dev-3.0 Kanban board, managed through the dev3 CLI (the same board this project ships). There is no separate issue tracker — a task is an issue. External GitHub PRs are pulled in as a secondary triage surface (see below).
triage-labels
The skills speak in terms of five canonical triage roles. On this repo the tracker is the dev-3.0 Kanban board (see docs/agents/issue-tracker.md), so each role is a dev3 label applied to the task. dev3 statuses/columns (todo, in-progress, user-questions, review-by-ai, review-by-user) are managed by hooks and are NOT…
planner
Specialized agent for creating detailed specifications and plans. Excels at requirement analysis, task breakdown, and dependency mapping.