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 tm-delivery-governancegit 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/tm-delivery-governance)<a href="https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/tm-delivery-governance"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/tm-delivery-governance/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/tm-delivery-governance"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/tm-delivery-governance.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.00056 | $0.00245 |
| Opus 5 | $0.00028 | $0.00122 |
| Sonnet 5 | $0.00011 | $0.00049 |
| Haiku 4.5 | $0.00006 | $0.00024 |
Grade A, and why
tm-delivery-governance 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
Technical Manager Delivery Governance
When to use
Use this skill when technical work spans multiple roles or requires delivery sequencing.
Rules
- Define workstreams, owner, file scope, dependency, and acceptance.
- Identify handoff points for TASK, REPORT, QA, PM, and ADMIN.
- Keep coordination separate from approval.
- Escalate governance decisions to PM or ADMIN.
Required output
Use docs/skills/technical-manager-playbook/delivery-governance.md.
Forbidden actions
- Do not archive, delete, or move lifecycle.
- Do not submit public GitHub issues.
- Do not assign unrelated file scope.
- Do not change PM runtime skills.
- Do not modify formal FCoP protocol.
Minimal example
Workstream: docs skill catalog
Owner: DEV
Dependency: PM review
Acceptance: manifest parses, skill validation passes
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 · 56 tokens per session scan A 8fe89c5a21b2
tm-delivery-governance is a skill published in the GitHub repository joinwell52-AI/CodeFlowMu-open (2 stars, last pushed 16d ago), licensed MIT. It adds 56 tokens to every session and 245 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.