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 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/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/breadchaincoop/labor.fun/pm-orchestration"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/pm-orchestration.svg" alt="Reviewed on agentmods" width="80" 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.5 | $0.00024 | $0.00471 |
| Sonnet 5.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 1mo 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.
- 1mo 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 yesterday), licensed MIT. It adds 60 tokens to every session and 1,177 once invoked, about $0.0002 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…