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 controlled-emergence-observergit 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/controlled-emergence-observer)<a href="https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/controlled-emergence-observer"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/controlled-emergence-observer.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.00084 | $0.00582 |
| Opus 5 | $0.00042 | $0.00291 |
| Sonnet 5 | $0.00017 | $0.00116 |
| Haiku 4.5 | $0.00008 | $0.00058 |
Grade A, and why
controlled-emergence-observer 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 8d 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
Controlled Emergence Observer
执行以 packages/evaluator/controlled-emergence-observer.js 为准；项目树检测执行 packages/evaluator/project-tree-observer.js。
观察输入
读取 TASK 的以下字段：
task_idparentthread_keyreferencessenderrecipientstatusbucket
优先读取 fcop/ledger/tasks.jsonl，因为 ledger 会将 references 归一化为 parent；以 _lifecycle/ TASK 文件作为兜底证据。
固定分类
- 资产异常：由 panel-scan 九类资产矩阵输出，不归类为 emergence。
controlled_emergence：probe、self-task 或 sandbox 自举模式。project_tree_emergence：同一thread_key下形成ADMIN→PM root → phase → PM→DEV/OPS/QA execution三层结构。
不要因为标题包含 Phase、project 或 probe 就判定涌现。必须由关系字段和角色链命中 detector。
项目树输出 Schema
emergence_type: project_tree_emergence
pattern: 主线任务 → 阶段任务 → 执行任务
root_task: TASK-xxx
phase_task: TASK-yyy
execution_tasks:
- TASK-zzz
value: FCoP 从任务流管理中涌现出产品演进树与项目管理能力。
risk: 独立 Phase 误挂旧主线时，archive 可能被 CHILD_TASKS_OPEN 拦截。
suggested_actions:
- 写入 emergence-log
- Panel 显示 Project / Phase / Execution 三层结构
- PM 创建 Phase 时提示继续当前主线或新建独立 thread
边界
- 不修改 lifecycle、ReportGate、TaskDispatcher 或 PM 派单流程。
- EVAL 只观察、记录和建议，不自行执行治理动作。
- 报告必须分别保留“受控涌现观察”和“项目树涌现观察”。
controlled_emergence与project_tree_emergence均可追加到fcop/internal/emergence-log.md。
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.
- 8d ago First seen · 56 lines · 84 tokens per session scan A a8cdf7f4e72b
controlled-emergence-observer is a skill published in the GitHub repository joinwell52-AI/CodeFlowMu-open (2 stars, last pushed 14d ago), licensed MIT. It adds 84 tokens to every session and 582 once invoked, about $0.0004 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
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
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.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…
ijfw-writing-skills
Authoring discipline for new IJFW skills. Use when creating a new skill, writing a skill, making a skill that does X, or asked to add a skill. Trigger: create a new skill, write a skill, new skill, make me a skill, skill that does, /ijfw-writing-skills.
ijfw-cross-audit
Generate a cross-platform multi-model audit (Trident) on a diff, brief, or artifact. Trigger: 'cross audit', 'Trident', 'second opinion', 'check with other models', 'check with other AIs', 'cross-check this', 'get another perspective', /cross-audit.