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 skills add richfrem/agent-plugins-skills --skill managing-github-issuesgit clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWrote 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/managing-github-issues)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/managing-github-issues"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/managing-github-issues/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/managing-github-issues"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/managing-github-issues.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.00121 | $0.01194 |
| Opus 5.5 | $0.00048 | $0.00478 |
| Sonnet 5.5 | $0.00024 | $0.00239 |
| Haiku 4.5 | $0.00012 | $0.00119 |
Grade A, and why
managing-github-issues 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 today.
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing GitHub Issues (managing-github-issues)
Create, promote, rank, propose and audit issues; report on GHAS without publishing changes.
Contents
- Constraints • Quick Start • Modes • Workflow • Verification • References
Constraints
- Dry-run first: every mutating script previews its payload; pass
--executeonly after review. - Redaction and taxonomy gates:
redaction_gate.pyblocks secrets; labels needtype:*,tier:*,source:*,risk:*andarea:*orplugin:*. - Body sections:
## Summary,## Observed Behavior,## Expected Behavior,## Evidence,## Impact. - Human gates:
propose-refactornever creates branches, commits or PRs;review-resolutionis read-only and never reopens or relabels. - Ledger: friction history lives in the repository's
map-debt.md(repository root, references folder).
Quick Start
python3 scripts/gh_issue_search.py --title "Bug summary" --area-label "area:dev-utils"
python3 scripts/gh_issue_create.py --title "Bug summary" --body "<5 sections>" --labels "type:friction,tier:1-friction,source:agent,risk:low,area:dev-utils"
Modes
| Mode | Script | Use for | Reference |
|---|---|---|---|
log |
gh_issue_search.py, gh_issue_create.py, gh_issue_comment.py, gh_issue_close.py |
Friction, bugs, map debt; dedupe into existing issues | log.md |
backlog |
task_to_issue_bridge.py |
Promote a local tasks/*.md note to an issue |
backlog.md |
prioritize |
gh_issue_prioritize.py |
Rank P0-P3 and sync Projects v2 fields | prioritize.md |
propose-refactor |
friction_cluster_agent.py (input) |
One systemic proposal per Tier 3 root cause | propose-refactor.md |
review-resolution |
gh issue list (read-only) |
Audit resolution:fixed / resolution:superseded issues |
review-resolution.md |
ghas-report |
GitHub connector or gh api (read-only) |
Report access, alerts, scanner coverage and repository security configuration | ghas-reporting-guide.md |
What ships with it
40 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 3.1 KB
- references/acceptance-criteria.md 2.9 KB
- references/backlog.md 1.6 KB
- references/bridge-guide.md 1003 B
- references/fallback-tree.md 2.2 KB
- references/ghas-reporting-guide.md 22 KB
- references/issue-taxonomy.json 1.3 KB
- references/issue-taxonomy.md 1.9 KB
- references/log.md 2.3 KB
- references/operation-catalog.md 2.5 KB
- references/prioritize.md 1.5 KB
- references/priority-matrix.md 1.3 KB
- references/propose-refactor.md 1.5 KB
- references/review-resolution.md 1.4 KB
- references/taxonomy-guide.md 797 B
- scripts/body_validator.py 1.1 KB runs code
- scripts/friction_cluster_agent.py 1.6 KB runs code
- scripts/gh_issue_close.py 3.4 KB runs code
- scripts/gh_issue_comment.py 2.4 KB runs code
- scripts/gh_issue_create.py 5.4 KB runs code
- scripts/gh_issue_prioritize.py 5.1 KB runs code
- scripts/gh_issue_search.py 4.1 KB runs code
- scripts/gh_issue_taxonomy_validate.py 2.8 KB runs code
- scripts/redaction_gate.py 1.4 KB runs code
- scripts/task_to_issue_bridge.py 7.6 KB 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_issue_prioritize.py 3.4 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
- tests/test_task_to_issue_bridge.py 3.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.
- today Changed c29882bd6636
- yesterday Changed · +4 lines · +13 tokens per session 24ad6bf7db9b
- 5d ago First seen · 67 lines · 108 tokens per session scan A 40daa7fbaad2
managing-github-issues is a skill published in the GitHub repository richfrem/agent-plugins-skills (7 stars, last pushed today), licensed MIT. It adds 121 tokens to every session and 1,194 once invoked, about $0.0005 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-10-24.
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.
gitlab-portfolio
Use when you need a single-pane cross-repo health view across all vault-registered GitLab and GitHub projects. Discovers repos from overview.md frontmatter in /01-projects//, aggregates open issues, MRs, critical labels, and stale signals via parallel glab/gh calls, then writes an idempotent PORTFOLIO.md dashboard.…
reset-epic
Reset an epic's test data — close PRs, delete branches, reopen issues, revert code.
mindforge-remove-workspace
Remove a MindForge workspace and clean up worktrees.