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/tqnonline/agent-forge/backlog-linearnpx skills add tqnonline/agent-forge --skill backlog-lineargit clone --depth 1 https://github.com/tqnonline/agent-forgeWhat 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.00134 | $0.01001 |
| Opus 5 | $0.00067 | $0.00500 |
| Sonnet 5 | $0.00027 | $0.00200 |
| Haiku 4.5 | $0.00013 | $0.00100 |
Grade A, and why
backlog-linear 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 2d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Backlog Exporter
Version: 1.0 | Role: Linear Issue 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 Linear via the Linear MCP server.
MCP tools used (available via Linear MCP server, not listed in allowed-tools):
list_teams, list_projects, list_issues, list_issue_labels, create_issue_label, save_issue
Prerequisites
- Platform-neutral backlog must exist at
{project}/specs/backlog/{epic-name}-backlog.md - If no backlog file exists, invoke
/backlog-decomposefirst - Linear MCP server must be connected
Phase 1: Gather Linear Context
Use AskUserQuestion to collect:
| Field | Required | Example |
|---|---|---|
| Team name | Yes | Platform Engineering |
| Project name | Yes | Q2 Auth Overhaul (or create new) |
| Cycle | No | Sprint 14 |
Then call list_teams and list_projects to confirm the team and project exist. If the project does not exist, confirm with user before creating it.
Phase 2: Cross-Reference
Avoid creating duplicate issues:
- Call
list_issueswith the team ID to retrieve all 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_labelsto check for existing labels - Create missing labels with
create_issue_label(e.g.,epic,feature,risk,impediment,ci-item)
Phase 3: Create Issues
Map backlog items to Linear issue fields:
| Backlog Field | Linear Field |
|---|---|
| Title | Title |
| Description + AC | Description (Markdown) |
| Priority (1/2/3) | Priority (Urgent/High/Medium/Low/None) |
| Work item type | Label |
| Story points | Estimate |
| Epic/Feature parent | Parent Issue ID |
Execute in order:
save_issuefor all parent-level items (epics, then features) -- capture returned issue IDssave_issuefor all child items (stories, technical stories) withparentIdset to parent issue IDsave_issuefor risks, impediments, and CI items withparentIdset to their linked epic
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.
- 2d ago First seen · 100 lines · 134 tokens per session scan A 036eedfe6e20
backlog-linear is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 3mo ago), licensed BSD-3-Clause. It adds 134 tokens to every session and 1,001 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…