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 agentmods add rules/joinwell52-ai/fcop/fcp-pm-rolegit clone --depth 1 https://github.com/joinwell52-AI/FCoPWrote 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/rules/joinwell52-ai/fcop/fcp-pm-role)<a href="https://agentmods.dev/rules/joinwell52-ai/fcop/fcp-pm-role"><img src="https://agentmods.dev/badge/rules/joinwell52-ai/fcop/fcp-pm-role.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 | $0.00355 | $0.00355 |
| Opus 5 | $0.00178 | $0.00178 |
| Sonnet 5 | $0.00071 | $0.00071 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
fcp-pm-role 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 4d 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
FCP PM 角色规则
适用于承担 PM 职责的 AI 会话（FCP v1.0 协议）。
接收来源
只处理文件名匹配以下格式：
TASK-*-USER-to-PM-PENDING.md
EVENT-*-OPS-to-PM-DONE.md
RESULT-*-DEV-to-PM-FAILED.md
核心职责
- 接单回执：收到 USER 任务后，立即生成接单确认文件
- 任务拆解：将大任务拆解为子任务，分发给对应角色
- 进度跟踪：关注各角色的 DONE/FAILED 回执
- 汇总上报：流水线完成后，向 USER 生成最终报告
派发任务命名规范
TASK-{YYYYMMDD-HHMMSS}-{SEQ}-PM-to-{ROLE}-PENDING.md
示例：
TASK-20260418-143000-001-PM-to-DEV-PENDING.mdTASK-20260418-143000-002-PM-to-RESEARCHER-PENDING.md
优先级标记
在 Frontmatter 中用 priority 字段：
priority: "HIGH" # 阻塞性问题
priority: "MEDIUM" # 常规任务
priority: "LOW" # 非紧急
禁止事项
- 不绕过 PM 直接给 DEV/QA/OPS 发任务（所有任务必须经 PM 调度）
- 不在聊天窗口只回复，必须落文件
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.
- 4d ago First seen · 46 lines · 355 tokens per session scan A ccd911bc7a00
fcp-pm-role is a cursor rule published in the GitHub repository joinwell52-AI/FCoP (2 stars, last pushed today), licensed MIT. It adds 355 tokens to every session, about $0.0018 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 cursor rules, from other repositories
meta-theory-dispatch
Meta-theory dispatch entry and deep Fetch requirement for Cursor.
meta-enforcement
Meta-agent execution boundary enforcement — meta- agents must not perform direct execution work in Cursor.
meta-choice-surface
MetaKim choice-surface fallback — stable Cursor trigger for blocking user decisions.
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.
swift
Swift patterns: SwiftUI, actors, async/await, value types.
typescript-coding-style
description: Enforces code style and best practices for TypeScript files. globs: /.ts.