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-acceptance-criteriagit 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-acceptance-criteria)<a href="https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/pm-acceptance-criteria"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/pm-acceptance-criteria/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/joinwell52-ai/codeflowmu-open/pm-acceptance-criteria"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/pm-acceptance-criteria.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.00049 | $0.00231 |
| Opus 5 | $0.00024 | $0.00115 |
| Sonnet 5 | $0.00010 | $0.00046 |
| Haiku 4.5 | $0.00005 | $0.00023 |
Grade A, and why
pm-acceptance-criteria 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 10d 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 Acceptance Criteria
When to use
Use this skill before sending work downstream or when reviewing a REPORT.
Rules
- Make acceptance checkable.
- Include function, file, behavior, evidence, and forbidden item checks.
- Require REPORT evidence when work claims completion.
- Keep lifecycle acceptance separate from business acceptance.
Required output
Use the checklist in docs/skills/pm-playbook/acceptance-criteria.md.
Forbidden actions
- Do not treat lifecycle state as business acceptance.
- Do not accept completion without evidence.
- Do not archive automatically.
- Do not delete audit files.
- Do not add adopted-pending
0003.
Minimal example
- [ ] JSON parses
- [ ] Required SKILL.md files exist
- [ ] Existing pm.* IDs unchanged
- [ ] No Panel/API changes
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.
- 10d ago First seen · 39 lines · 49 tokens per session scan A ee848433de6b
pm-acceptance-criteria is a skill published in the GitHub repository joinwell52-AI/CodeFlowMu-open (2 stars, last pushed 16d ago), licensed MIT. It adds 49 tokens to every session and 231 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-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
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.