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 skills/richfrem/agent-plugins-skills/github-issue-backlog-agentnpx skills add richfrem/agent-plugins-skills --skill github-issue-backlog-agentgit 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/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.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.00083 | $0.00682 |
| Opus 5 | $0.00042 | $0.00341 |
| Sonnet 5 | $0.00017 | $0.00136 |
| Haiku 4.5 | $0.00008 | $0.00068 |
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 yesterday.
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 — 68 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)
Routing Directive: USE ONLY when promoting ephemeral single-session local tasks (
tasks/*.md) into durable tracked GitHub Issues. DO NOT USE for managing local kanban boards (usetask-agentinstead) or directly creating/searching issues from execution friction (usegithub-issue-agentinstead).
The github-issue-backlog-agent skill bridges local task scratch items into durable GitHub Issues. It parses local task markdown files, constructs evidence-backed markdown bodies conforming to repository taxonomy guidelines, and invokes gh_issue_create.py in dry-run or live mode.
Safety & Security Contracts
- Dry-Run Execution Default (
execute=False): By default, callingtask_to_issue_bridge.pyoutputs a structured JSON payload detailing the issue title, body, and labels without creating a live GitHub issue. Live creation requires--execute. - Taxonomy Enforcement: Every escalated issue is validated against
issue-taxonomy.jsonrules (type:*,tier:*,source:*,risk:*, andarea:*/plugin:*). - Secret Redaction: Both title and body undergo secret scanning via
redaction_gate.pyprior to payload generation or issue submission.
Usage catalog
Promote Task Scratch Item to GitHub Issue
- Helper Script:
plugins/dev-utils/skills/github-issue-backlog-agent/scripts/task_to_issue_bridge.py - CLI Usage:
# Dry-run payload preview: python3 plugins/dev-utils/skills/github-issue-backlog-agent/scripts/task_to_issue_bridge.py \ --task-path tasks/backlog/0042-fix-deadlock.md \ --labels "area:dev-utils,tier:2-structural" # Live issue creation: python3 plugins/dev-utils/skills/github-issue-backlog-agent/scripts/task_to_issue_bridge.py \ --task-path tasks/backlog/0042-fix-deadlock.md \ --labels "area:dev-utils,tier:2-structural" \ --execute
Python API Interface
from pathlib import Path
from plugins.dev_utils.skills.github_issue_backlog_agent.scripts.task_to_issue_bridge import promote_task_to_issue
result = promote_task_to_issue(
task_path=Path("tasks/backlog/0042-fix-deadlock.md"),
extra_labels=["area:dev-utils", "tier:2-structural"],
execute=False, # Dry-run default
)
What ships with it
3 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.
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.
- yesterday 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 (6 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 682 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
kapso-whatsapp
How to interact with Kapso WhatsApp from the swarm — read inbound webhook payloads (text AND media), fetch message history, send free-form messages within the 24h session window (and template messages outside it), mark-as-read, show the typing indicator, send reactions, download media, verify webhook signatures, and…
composio
Use Composio from Agent Swarm through the agent-swarm x composio CLI route, the swarmx MCP tool, or a registered ctx.api.composio script connection. Trigger when a task needs connected third-party app tools such as Gmail, Google Calendar, Google Docs, Google Drive, GitHub, Slack, Notion, or HubSpot through Tool Router…
attio-interaction
Generic Attio CRM REST API v2 recipes for querying records, upserting companies/people/deals, writing notes/tasks/comments, managing lists, and handling webhooks.
swarm-scripts
Bulk, repeat, fan-out, or data-heavy work: write and run swarm scripts (inline script-run, named script-upsert, durable launch-script-run). Covers the script-vs-tool rubric, the authoring contract (args first, ctx second), the seed catalog, connections and secrets, dbquery, and exposing a script as an API.
user-management
How to manage the user registry — creating users for new Slack/GitHub/GitLab/Linear identities, managing aliases, resolving users across platforms. Use when a new human interacts with the swarm or when user identity needs updating.
scheduled-task-resilience
Guardrails for polling, scheduled jobs, and long-running external operations. Use whenever a task waits on CI, builds, deploys, browser jobs, or another asynchronous API so work survives heartbeat checks without duplicate delivery.