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/joshsmithxrm/power-platform-developer-suite/backlognpx skills add joshsmithxrm/power-platform-developer-suite --skill backloggit clone --depth 1 https://github.com/joshsmithxrm/power-platform-developer-suiteWrote 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/joshsmithxrm/power-platform-developer-suite/backlog)<a href="https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/backlog"><img src="https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/backlog.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.00039 | $0.00660 |
| Opus 5 | $0.00019 | $0.00330 |
| Sonnet 5 | $0.00008 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
backlog 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog
Manage GitHub issues using the label taxonomy, milestone conventions, and triage rules defined in docs/BACKLOG.md.
When to Use
- "Create an issue for X"
- "File a bug for X"
- "Triage the backlog"
- "Groom issues"
- "What should we work on next?"
- "Review backlog priorities"
- After completing work that reveals follow-up issues
Reference
Read docs/BACKLOG.md at the start of every backlog operation - it is the source of truth for labels, milestones, and rules.
Read REFERENCE.md §1 "Label taxonomy" before classifying any issue.
Process
1. Parse Arguments
/backlog create <description>- create a new issue/backlog triage- triage untriaged inbox/backlog review- review backlog for promotion/backlog validate- verify open issues are still valid/backlog(no args) - show backlog summary
2. Read Rules
cat docs/BACKLOG.md
3. Execute Operation
Create Issue
- Determine
type:label (bug/enhancement/docs/performance/refactor) - Determine
area:label (auth/cli/data/extension/plugins/tui) - Ask user for milestone or default to none
- Check if an
epic:label applies - Ask user for
priority:label if not obvious - Create:
gh issue create --title "<title>" --body "<body>" --label "type:<type>,area:<area>" --milestone "<milestone>"
If no milestone, add status:backlog. Every issue must have at minimum one type: + one area: + either a milestone or status: label.
Triage Inbox
gh issue list --state open --limit 200 --json number,title,labels,milestone --jq '[.[] | select(.milestone == null) | select(.labels | map(.name) | any(startswith("status:")) | not)]'
Read REFERENCE.md §2 "Mandatory verification" for the per-issue checklist before presenting any issue to the user. Read REFERENCE.md §3 "Triage decision rules" for the categorization heuristic.
Review Backlog
Surface ready-to-promote issues from status:backlog based on completion criteria + dependency satisfaction. See REFERENCE.md §4 "Promotion rules".
What ships with it
1 file 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 · 78 lines · 39 tokens per session scan A 18a1c094abbc
backlog is a skill published in the GitHub repository joshsmithxrm/power-platform-developer-suite (5 stars, last pushed 11d ago), licensed MIT. It adds 39 tokens to every session and 660 once invoked, about $0.0002 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
issue-triage
Queries and triages open GitHub issues that need attention. Helps identify issues needing milestones, labels, or investigation.
agentic-labeler
Labels issues and pull requests in the dotnet/maui repository with area- and platform/ labels ONLY, based on technical content and platform-file conventions. Used by the gh-aw agentic-labeler workflow and available for batch evaluation and interactive Copilot CLI usage.
create-issue
Create a GitHub issue with labels and optional sub-issues.
discover-work
Deep research across codebase, GitHub issues, discussions, project board, and architecture docs to discover new tasks, gaps, technical debt, and improvement ideas. Trigger when user says: discover work, find tasks, what needs doing, audit codebase, find gaps, technical debt audit, backlog discovery, brainstorm tasks…
collattice
Operate a Collattice kanban board through its Model Context Protocol (MCP) endpoint — connecting, authentication, the board model, identifier rules (board-level reads need a board GUID, not a slug), the Markdown a board renders, and the full tool reference: reading and creating cards, moving and reordering lanes…
agentweaver-issue-status
Print a live pipeline status board for GitHub issues — showing each issue's assigned agent, current status (backlog/implementing/RCA/merged), merge commit SHA, whether it has been deployed to the cluster, and docs disposition. Use this skill whenever the user asks for a status report, status board, tracking table…