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-adonpx skills add tqnonline/agent-forge --skill backlog-adogit 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-ado)<a href="https://agentmods.dev/skills/tqnonline/agent-forge/backlog-ado"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/backlog-ado.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.00175 | $0.01289 |
| Opus 5 | $0.00088 | $0.00645 |
| Sonnet 5 | $0.00035 | $0.00258 |
| Haiku 4.5 | $0.00017 | $0.00129 |
Grade A, and why
backlog-ado 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 4d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure DevOps Backlog Exporter
Version: 1.0 | Role: Azure DevOps SAFe Backlog Specialist Methodology: Gather Context > Map Fields > Generate Workbook > Deliver
You take platform-neutral backlog files produced by backlog-decompose and transform them into Azure DevOps SAFe-compliant Excel workbooks ready for CSV import.
Prerequisites
- Platform-neutral backlog must exist at
{project}/specs/backlog/{epic-name}-backlog.md - If no backlog file exists, invoke
/backlog-decomposefirst - xlsx skill for workbook generation
- scripts/ado_workbook_builder.py (optional) for automated workbook assembly via Bash
Phase 1: Gather ADO Context
Use AskUserQuestion to collect:
| Field | Example |
|---|---|
| Area Path | MyProject\TeamA |
| Iteration Path prefix | MyProject\PI-4\Sprint- |
| PI or Release number | PI-4 or Release 2.1 |
| Default Priority | 1 (Must), 2 (Should), or 3 (Could) |
Phase 2: Map to ADO SAFe Fields
Read the backlog file and map each work item to its ADO-specific field schema. All 7 types use the SAFe process template fields. Key fields per type:
- Epic: Title, Description, Expected Benefits, Measure Indicators, Area, Iteration, Priority, Risk, Value Area, Start/Target Date, State
- Feature: Title, Description, Business Drivers, Critical Value, In Scope, Out of Scope, Priority, Risk, Effort, Business Value, Time Criticality, Value Area
- User Story: Title, Description (As a/I want/So that), Issues and Assumptions, Acceptance Criteria, Story Points, Priority, Risk, Release Number, Value Area (Business)
- Technical User Story: Same as User Story but Value Area = Architectural, State Reason = "Moved to state New"
- Risk: Title, Description, Business Impact, Likelihood (1-5), Impact (A-E), Risk Assessment (1-5), Mitigation Plan
- Impediment: Title, Description (What is blocked), Cause, Business Impact, Possible Solutions, Resolution, Priority, State
- CI Item: Title, Description, Expected Benefit
What ships with it
5 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.
- 4d ago First seen · 112 lines · 175 tokens per session scan A cd9ec462f815
backlog-ado is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 3mo ago), licensed BSD-3-Clause. It adds 175 tokens to every session and 1,289 once invoked, about $0.0009 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
slack-report-delivery
Deliver formatted network reports, audit results, topology diagrams, and compliance documentation to Slack channels with rich Block Kit formatting. Use when posting a health check report, sharing a security audit, delivering topology diagrams, or sending scheduled network reports to Slack.
google-workspace-ops
Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.
google-workspace-ops
Operate across Google Workspace tools with reusable patterns for docs, sheets, calendar, drive, and gmail.
portfolio-ingest
Extract portfolio entities and structured context from uploaded documents (uploads/ folder). Use whenever the user mentions uploading files, importing documents, ingesting data, "I have some files", "parse these docs", "use these docs as input", "internal documents", "background material", "here's our strategy deck"…
aaif-sync-chapters
Push intake decisions out of the Intake Ops sheet — accepted organizers onto the Chapters List and into each chapter's About doc, intake people plus their survey interest into their chapter's Attendee CRM (accepted people always; organizer candidates only where the chapter is big enough to self-serve), per-chapter…
estimate
개발 견적서 자동 생성. 젭마인 산출물(spec, sections, api-spec)에서 기능을 추출하고, 비용 그룹별(개발비, 인건비, 클라우드, API, 잡비) 견적서를 엑셀로 출력. /estimate로 실행.