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 tqnonline/agent-forge --skill backlog-githubgit clone --depth 1 https://github.com/tqnonline/agent-forgeWrote 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/tqnonline/agent-forge/backlog-github)<a href="https://agentmods.dev/skills/tqnonline/agent-forge/backlog-github"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/backlog-github/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/tqnonline/agent-forge/backlog-github"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/backlog-github.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.00149 | $0.01049 |
| Opus 5.5 | $0.00060 | $0.00420 |
| Sonnet 5.5 | $0.00030 | $0.00210 |
| Haiku 4.5 | $0.00015 | $0.00105 |
Grade A, and why
backlog-github 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 2mo 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues Backlog Exporter
Version: 1.0 | Role: GitHub Issues Creation Specialist Methodology: Gather Context > Cross-Reference > Create Issues > Verify
You take platform-neutral backlog files produced by backlog-decompose and create issues directly in GitHub via the GitHub MCP server.
MCP tools used (available via GitHub MCP server, not listed in allowed-tools):
list_issues, search_issues, list_issue_types, issue_write, sub_issue_write
Prerequisites
- Platform-neutral backlog must exist at
{project}/specs/backlog/{epic-name}-backlog.md - If no backlog file exists, invoke
/backlog-decomposefirst - GitHub MCP server must be connected
Phase 1: Gather GitHub Context
Use AskUserQuestion to collect:
| Field | Required | Example |
|---|---|---|
| Repository owner/name | Yes | acme-corp/platform-api |
| Milestone | No | v2.1 |
Phase 2: Cross-Reference
Avoid creating duplicate issues:
- Call
list_issuesfor the target repository to retrieve open issues - Compare generated backlog titles against existing issues using fuzzy matching
- Flag potential duplicates -- ask user: skip, update existing, or create new
- Call
list_issue_typesto verify available issue types for the repository - Confirm label and milestone availability; note any that need manual creation
Phase 3: Create Issues
Map backlog items to GitHub issue fields:
| Backlog Field | GitHub Field |
|---|---|
| Title | Title |
| Description + AC | Body (Markdown with acceptance criteria) |
| Work item type | Label (e.g., epic, feature, user-story, risk) |
| Priority (1/2/3) | Label (e.g., priority:must, priority:should, priority:could) |
| Story points | Label (e.g., points:5) or body metadata |
| Milestone | Milestone |
| Work item type | Issue Type (if available) |
Execute in order:
issue_writefor all parent-level items (epics, then features) -- capture returned issue numbersissue_writefor all child items (stories, technical stories, risks, impediments, CI items)sub_issue_writeto establish parent-child hierarchy using captured issue numberssearch_issuesto verify all items were created successfully
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.
- 2mo ago First seen · 99 lines · 149 tokens per session scan A fd85d7a876af
backlog-github is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 5mo ago), licensed BSD-3-Clause. It adds 149 tokens to every session and 1,049 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…