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-backlog-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-backlog-agent)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/github-issue-backlog-agent"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/github-issue-backlog-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-backlog-agent"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/github-issue-backlog-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.00069 | $0.00697 |
| Opus 5.5 | $0.00028 | $0.00279 |
| Sonnet 5.5 | $0.00014 | $0.00139 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
github-issue-backlog-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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Backlog Agent (github-issue-backlog-agent)
Escalates ephemeral single-session local tasks (tasks/*.md) into durable, taxonomy-validated GitHub Issues.
Contents
Critical Constraints
- Scope Boundary: USE ONLY for promoting local tasks (
tasks/*.md) into durable backlog issues. DO NOT USE for general friction queries (usegithub-issue-agent). - Dry-Run by Default: Generate and preview issue payloads without
--executebefore committing live issues. - Redaction Gate: Task descriptions and logs must pass secret scanning (
redaction_gate.py) prior to export. - Mandatory Labels: Issues must be tagged with explicit
area:*orplugin:*andtier:*dimensions.
Quick start
# Preview task escalation to GitHub issue payload (dry-run)
python3 plugins/dev-utils/skills/github-issue-backlog-agent/scripts/task_to_issue_bridge.py \
--task-path tasks/backlog/<task-file>.md \
--labels "area:dev-utils,tier:2-structural"
# Execute live issue creation
python3 plugins/dev-utils/skills/github-issue-backlog-agent/scripts/task_to_issue_bridge.py \
--task-path tasks/backlog/<task-file>.md \
--labels "area:dev-utils,tier:2-structural" \
--execute
Workflow
- Phase 1: Task Parsing: Read the local task markdown file, extracting objective, observed blocker, and repro context.
- Phase 2: Payload Formatting: Construct structured sections (
Summary,Observed Behavior,Expected Behavior,Evidence,Impact). - Phase 3: Validation & Gate Check: Run
task_to_issue_bridge.pyin dry-run mode to verify redaction and taxonomy validity. - Phase 4: Live Creation & Task Reference: Run with
--executeand record the generated issue URL into the local task notes.
Verification
# Audit skill compliance
python3 plugins/agent-scaffolders/scripts/audit_skill.py plugins/dev-utils/skills/github-issue-backlog-agent --mode source
What ships with it
10 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 631 B
- references/acceptance-criteria.md 69 B
- references/bridge-guide.md 62 B
- references/fallback-tree.md 63 B
- scripts/body_validator.py 34 B runs code
- scripts/gh_issue_create.py 35 B runs code
- scripts/gh_issue_taxonomy_validate.py 46 B runs code
- scripts/redaction_gate.py 34 B runs code
- scripts/task_to_issue_bridge.py 40 B 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.
- 17d ago Changed · +18 lines babf4506197f
- 1mo ago Changed · -17 lines · -14 tokens per session de3ddc24b933
- 1mo ago First seen · 68 lines · 83 tokens per session scan A 70a8011b07b5
github-issue-backlog-agent is a skill published in the GitHub repository richfrem/agent-plugins-skills (7 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 697 once invoked, about $0.0003 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.