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 joinwell52-AI/CodeFlowMu-open --skill pm-priority-triagegit clone --depth 1 https://github.com/joinwell52-AI/CodeFlowMu-openWrote 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/joinwell52-ai/codeflowmu-open/pm-priority-triage)<a href="https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/pm-priority-triage"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/pm-priority-triage.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.00057 | $0.00235 |
| Opus 5 | $0.00028 | $0.00118 |
| Sonnet 5 | $0.00011 | $0.00047 |
| Haiku 4.5 | $0.00006 | $0.00023 |
Grade A, and why
pm-priority-triage 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 7d 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.
What it actually says
PM Priority Triage
When to use
Use this skill when multiple tasks or risks compete, or when ADMIN asks what should happen next.
Rules
- P0 blocks main flow or risks governance/data damage.
- P1 affects quality or maintainability without blocking main flow.
- P2 is optimization, documentation, or later enhancement.
- State owner and suggested action.
Required output
Use the structure in docs/skills/pm-playbook/priority-triage.md.
Forbidden actions
- Do not treat PM priority advice as ADMIN decision.
- Do not let EVAL promote itself.
- Do not submit public GitHub issues automatically.
- Do not bypass ADMIN.
Minimal example
Issue: missing REPORT evidence
Priority: P1
Owner: DEV
Action: request fixed report with evidence
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.
- 7d ago First seen · 38 lines · 57 tokens per session scan A 0962c56afde6
pm-priority-triage is a skill published in the GitHub repository joinwell52-AI/CodeFlowMu-open (2 stars, last pushed 13d ago), licensed MIT. It adds 57 tokens to every session and 235 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
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
init-workspace-flow
Workflow for initializing or upgrading a workspace: context, discovery, documentation, etc.
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.