Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/richfrem/agent-plugins-skillsnpx agentmods add skills/richfrem/agent-plugins-skills/github-issue-agentWrote 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/skills/richfrem/agent-plugins-skills/github-issue-agent)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/github-issue-agent"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/github-issue-agent/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/skills/richfrem/agent-plugins-skills/github-issue-agent"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/github-issue-agent.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.00101 | $0.00900 |
| Opus 5.5 | $0.00040 | $0.00360 |
| Sonnet 5.5 | $0.00020 | $0.00180 |
| Haiku 4.5 | $0.00010 | $0.00090 |
Grade A, and why
github-issue-agent 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 17d 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Agent (github-issue-agent)
Provides safe, deduplicated, root-cause-consolidated, and taxonomy-validated logging of repository execution friction, map debt, and bugs into GitHub Issues.
Contents
Critical Constraints
- Scope Boundary: USE ONLY for durable repository bugs, execution friction (T1-T3), map debt, and architectural improvements. DO NOT USE for worktrees (use
github-issue-worktree-agent) or PR lifecycles (usegithub-issue-pr-lifecycle-agent). - Dry-Run by Default: All issue operations generate payloads in dry-run mode unless
--executeis explicitly passed. - Secret Redaction Gate: Submissions containing API keys, private tokens, or credentials are strictly blocked by
redaction_gate.py. - Taxonomy Validation: All issues require explicit dimensions:
type:*,tier:*,source:*,risk:*, andarea:*orplugin:*. - Structured Sections: Bodies must include
## Summary,## Observed Behavior,## Expected Behavior,## Evidence, and## Impact.
Quick start
# Search related issues for deduplication
python3 plugins/dev-utils/skills/github-issue-agent/scripts/gh_issue_search.py \
--title "Bug summary" --area-label "area:dev-utils"
# Generate validated issue payload (dry-run)
python3 plugins/dev-utils/skills/github-issue-agent/scripts/gh_issue_create.py \
--title "Bug summary" \
--body "## Summary\n...\n## Observed Behavior\n...\n## Expected Behavior\n...\n## Evidence\n...\n## Impact\n..." \
--labels "type:friction,tier:1-friction,source:agent,risk:low,area:dev-utils"
Workflow
- Phase 1: Search & Deduplication: Execute
gh_issue_search.pyusing title keywords and area labels to consolidate into existing open issues. - Phase 2: Payload Generation: Structure the 5 mandatory markdown sections and assign the full taxonomy label set.
- Phase 3: Validation & Redaction: Run
redaction_gate.pyandbody_validator.pyto ensure zero secrets and compliant formatting. - Phase 4: Submission or Comment: If root-cause exists, append evidence via
gh_issue_comment.py; otherwise create new issue with--execute.
What ships with it
28 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/evals.json 851 B
- references/acceptance-criteria.md 61 B
- references/fallback-tree.md 55 B
- references/issue-taxonomy.json 39 B
- references/issue-taxonomy.md 37 B
- references/operation-catalog.md 59 B
- references/taxonomy-guide.md 56 B
- scripts/body_validator.py 34 B runs code
- scripts/friction_cluster_agent.py 42 B runs code
- scripts/gh_issue_close.py 34 B runs code
- scripts/gh_issue_comment.py 36 B runs code
- scripts/gh_issue_create.py 35 B runs code
- scripts/gh_issue_search.py 35 B runs code
- scripts/gh_issue_taxonomy_validate.py 46 B runs code
- scripts/redaction_gate.py 34 B runs code
- templates/bug-issue.md 332 B
- templates/doc-gap-issue.md 455 B
- templates/enhancement-issue.md 381 B
- templates/friction-issue.md 473 B
- templates/map-debt-issue.md 448 B
- tests/test_dedup_search.py 3.7 KB runs code
- tests/test_friction_cluster.py 1.5 KB runs code
- tests/test_gh_issue_close.py 2.6 KB runs code
- tests/test_gh_issue_create.py 1.8 KB runs code
- tests/test_gh_mocked_cli.py 6.8 KB runs code
- tests/test_issue_body_rendering.py 1.8 KB runs code
- tests/test_issue_taxonomy.py 1.6 KB runs code
- tests/test_secret_redaction.py 2.1 KB runs code
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.
- 17d ago Changed · +15 lines 9dd6eae466da
- 1mo ago Changed · -43 lines · +21 tokens per session dd7038fb89ba
- 1mo ago Changed 65923af7e530
- 1mo ago First seen · 101 lines · 80 tokens per session scan A 3ff0e92947ad
github-issue-agent is a skill published in the GitHub repository richfrem/agent-plugins-skills (7 stars, last pushed yesterday), licensed MIT. It adds 101 tokens to every session and 900 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
factory-handoff
Hand one exact agent-ready ticket to the central Factory runtime over the configured SSH forced-command boundary. Use when an operator asks to hand off an existing ticket or a prose request instead of implementing it in the current session.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
linear-cli
Use when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write boundaries.
gh-issues
Use when creating, searching, updating, or managing GitHub issues via CLI. Triggers: "issue", "create issue", "gh issue", "task tracking", "context", "handoff", "resume task", "session context", "save progress", "active tasks", "in-progress", "my tasks", "open issues". Covers: gh commands, bulk operations, JSON/jq…
development-scheduler
A workflow for coordinating multi-role coding work through Herdr, a task scheduler, and repo-harness sessions. It assigns implementation, review, and handoff tasks while checking permissions and evidence.