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 jrjsmrtn/project-orchestration-skills --skill graduate-backloggit clone --depth 1 https://github.com/jrjsmrtn/project-orchestration-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/jrjsmrtn/project-orchestration-skills/graduate-backlog)<a href="https://agentmods.dev/skills/jrjsmrtn/project-orchestration-skills/graduate-backlog"><img src="https://agentmods.dev/badge/skills/jrjsmrtn/project-orchestration-skills/graduate-backlog/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/jrjsmrtn/project-orchestration-skills/graduate-backlog"><img src="https://agentmods.dev/badge/skills/jrjsmrtn/project-orchestration-skills/graduate-backlog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00124 | $0.05123 |
| Opus 5 | $0.00062 | $0.02561 |
| Sonnet 5 | $0.00025 | $0.01025 |
| Haiku 4.5 | $0.00012 | $0.00512 |
Grade A, and why
graduate-backlog scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
use the Gitea REST API via `curl` + token (`/api/v1/repos/{owner}/{repo}/…`) for anything `tea` How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog Graduation
Bridge a project's in-repo backlog onto a forge issue tracker at the moment the backlog
outgrows a single contributor. The orchestration skills author a rich in-repo backlog —
docs/roadmap/roadmap.md (phases → target versions → task lists), docs/sprints/*.md
(plans/retrospectives), a Nygard ADR sequence, and a Keep-a-Changelog CHANGELOG.md. Once more
than one person needs to see and claim that work, they need a tracker — but that transform is
manual and uncodified.
This skill performs it conservatively. The default is thin-hybrid: planning stays in-repo,
and the tracker holds only incoming/reactive work plus — at most — the current milestone's tactical
items. That is light externalization, not a board build-out. A richer board is opt-in (the
roadmap-visible level), justified by a real need for roadmap visibility.
The trigger is team scale, not exposure. Graduation is driven by who needs to see the work — the same signal as the t0→t1 tier bump ("more than one contributor"). It is not gated on the Public distribution profile: a corporate team on an internal GitLab needs a board without ever open-sourcing, and a solo public repo may never need one. Exposure gates compliance controls, not work organization. (Workspace decision records: "Distribution-Profile Axis for Compliance Qualification", "Work-Organization Graduation: Thin-Hybrid Backlog Externalization", "Plugin Taxonomy by Lifecycle, Not Exposure" — cited by title because bare numbers would collide with the target project's own ADR sequence, which Phase 3 writes into.)
Establish vs operate. This skill establishes tracker structure from the backlog;
incoming-issue(project-maintenance-skills) operates it afterward. Where that plugin is installed it owns the richer contributor-facing setup — issue templates,good first issue, the full triage taxonomy. This skill creates only the minimal labels it needs, so it works standalone in contexts where the maintenance plugin is absent.
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.
- 12d ago First seen · 334 lines · 124 tokens per session scan A 0798fb90de0e
graduate-backlog is a skill published in the GitHub repository jrjsmrtn/project-orchestration-skills (15 stars, last pushed 8d ago), licensed MIT. It adds 124 tokens to every session and 5,123 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
c-jira
Manage Jira issues using jira (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.
linear
Linear project management — issues, cycles, and projects via GraphQL API.
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).
flow-next-flow
Attended conductor for an idea, change request, spec or task id, tracker issue, branch or path, bug report, how or why question, slowness, cleanup, or design fork. Use when no skill is named.
meegle
A guide and command-line interface for managing Feishu/Lark Meego project data, including work items, workflow steps, views, personal tasks, and schedules. Feishu/Lark is a collaboration platform, while Meego is its project-management system.
triage
Work-unit triage for GitHub issues. Groups raw issues, fuses each group with the AGENTS.md northstar, and externalizes each routed unit to a substrate record a collaborator session is pointed at.