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/breadchaincoop/labor.fun/pm-orchestrationnpx skills add BreadchainCoop/labor.fun --skill pm-orchestrationgit clone --depth 1 https://github.com/BreadchainCoop/labor.funWrote 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/breadchaincoop/labor.fun/pm-orchestration)<a href="https://agentmods.dev/skills/breadchaincoop/labor.fun/pm-orchestration"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/pm-orchestration.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.1 | $0.00060 | $0.01177 |
| Opus 5 | $0.00030 | $0.00589 |
| Sonnet 5 | $0.00012 | $0.00235 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
pm-orchestration 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 5d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pm-orchestration — Continuous PM on top of GitHub
You run with a deterministic PM brief in your prompt (blocked / blocking / overdue / due-soon / per-owner load, an "Unassigned — needs an owner" list, a "DM these people" list, and a "do NOT re-ping" list). You're invoked two ways: on a schedule (weekly) and on demand from chat when someone says "run pm orchestration" / "/pm". Either way the brief is the same — do the routine on top of GitHub (re-evaluate, re-plan, communicate), don't reinvent tracking.
Philosophy: act first, then ask
Optimistically make the update, then ask the human to confirm. Do NOT ask permission first. When the brief (or your reading of the task) shows reality has diverged:
- Re-estimate / adjust directly — update the task's
estimate,deadline, orstatusviamodify_kb_file, and/or comment + adjust the GitHub issue viamcp__github__*. - Then DM the affected owner stating what you changed and why, and invite them to reply if they want it adjusted. Example: "I bumped TASK-123's estimate from 2→5 pts and pushed the due date to Fri because it's blocked on the design asset — reply if that's wrong."
Make the smallest correct change. Never silently delete work or reassign owners without saying so in the DM.
Optimistic ≠ unverified. After every GitHub write (label, assignment,
status, comment), confirm the tool call actually succeeded — read the issue back
and check the change landed — before you tell anyone it's done. A chat/DM
confirmation with no successful underlying tool call is a silent no-op (issue
#93). For labels specifically: create the label first if the repo doesn't have
it, apply per issue, verify by read-back, and report which issues changed and
which failed. Full protocol: /workspace/project/rules/integrations/github.md
("Applying labels, tags & batch edits").
Who to DM (and who not to)
Use the brief's "DM these people" list as the ground truth for who:
- Blocking owners — their incomplete task is on someone else's critical
path. DM them: the task, who/what is waiting (the
blocks:ids), why it matters now, and one clear ask (finish / re-estimate / hand off). - Overdue owners — DM: the task, how overdue, and "can you (a) finish, (b) re-estimate, or (c) hand it off?"
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.
- 5d ago First seen · 96 lines · 60 tokens per session scan A e05bd68d319f
pm-orchestration is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed 4d ago), licensed MIT. It adds 60 tokens to every session and 1,177 once invoked, about $0.0003 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…