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-evolve-skillsgit 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-evolve-skills)<a href="https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/pm-evolve-skills"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/pm-evolve-skills/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-evolve-skills"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/pm-evolve-skills.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.00059 | $0.00765 |
| Opus 5 | $0.00030 | $0.00382 |
| Sonnet 5 | $0.00012 | $0.00153 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
pm-evolve-skills 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 9d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Skill Evolution
Treat capability gaps as work to resolve, not as a reason to guess or immediately hand the problem back to ADMIN.
Workflow
- State the required capability precisely. Distinguish missing knowledge, missing procedure, missing tool access, and missing permission.
- Inventory what is already available:
- MCP tools and their schemas.
.codeflowmu/agent-skills.manifest.json.- Relevant
skills/*/SKILL.mdpackages. - Repository code, tests, docs, examples, and prior evidence.
- Use
skill_searchto search the local library, GitHub, and the public web when the capability is not already known.
- Select the smallest credible learning source. Prefer source code, tests, official documentation, and proven local examples.
- Load only the relevant Skill or documentation. Do not flood context with the whole catalog.
- Use
skill_learnwith selected local skill ids and source URLs to build a traceable learning pack.
- Use
- Learn by doing: run a minimal experiment, build a small example, inspect a real artifact, or execute a reversible probe.
- Verify the result against an explicit expectation. Record failures and uncertainty honestly.
- Apply the capability to the current problem.
- Retain reusable learning:
- Update or create a focused Skill when the procedure will recur.
- Add a template or example when structure matters.
- Record a proposal when installation, permission, or architectural change requires approval.
- Use
skill_publishonly after a real validation succeeds. Include validation evidence and source URLs; do not overwrite an existing Skill implicitly.
- Reuse retained knowledge on later tasks instead of rediscovering it.
Product / UI capability gaps
Weak product planning is a capability gap. If PM cannot confidently define product positioning, user value, information architecture, interaction flow, visual direction, mobile/PWA/Gateway delivery boundary, or acceptance evidence, PM must:
- Load
pm-product-design-brief. - Check the relevant UI playbook packages:
ui-requirementsui-information-architectureui-visual-consistencyui-usability-acceptance
- Inspect nearby successful product examples or reports before dispatch.
- Produce a concrete design brief, then dispatch DEV / QA / OPS.
- If the pattern will recur, refine the Playbook or create a smaller reusable template after validation.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 70 lines · 59 tokens per session scan A 23c6b348afc7
pm-evolve-skills is a skill published in the GitHub repository joinwell52-AI/CodeFlowMu-open (2 stars, last pushed 15d ago), licensed MIT. It adds 59 tokens to every session and 765 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
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.