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.
git clone --depth 1 https://github.com/xyzbit/AI-CodingWrote 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/xyzbit/ai-coding/p-task-splitting)<a href="https://agentmods.dev/rules/xyzbit/ai-coding/p-task-splitting"><img src="https://agentmods.dev/badge/rules/xyzbit/ai-coding/p-task-splitting/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/rules/xyzbit/ai-coding/p-task-splitting"><img src="https://agentmods.dev/badge/rules/xyzbit/ai-coding/p-task-splitting.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.00008 | $0.00467 |
| Opus 5.5 | $0.00003 | $0.00187 |
| Sonnet 5.5 | $0.00002 | $0.00093 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
p-task-splitting 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 1mo 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
任务拆分规则 (Task Splitting Guidelines)
规则目的
本规则旨在指导如何科学、合理地将大型需求拆分为可管理和执行的任务单元。
任务拆分流程
1. 任务分析与拆分
- 拆分维度
按照当前需求选择合适的拆分方式，参考下面两种：
1. 功能模块维度 - 核心流程功能点 - 辅助功能点 - 扩展功能点 2. 业务流程维度 - 上游数据处理 - 核心业务逻辑 - 下游数据输出
2. 任务描述规范
- 任务格式
[ ] 任务标题 - 描述：具体的任务描述 - 输入：任务的输入项 - 输出：预期的输出结果 - 依赖：其他任务的依赖关系 - 示例
[ ] 用户登录模块开发 - 描述：实现用户名密码登录功能 - 输入：用户名、密码 - 输出：登录态token - 依赖：用户服务、认证服务
3. 任务确认流程
- 确认步骤
1. 任务评审 - 与用户确认功能细节 2. 任务状态更新 - [ ] -> [x] 表示任务完成
4. 任务验收标准
- 确认功能和质量是否过关
- 同用户进行任务是否完成的确认
注意事项
- 任务粒度控制
- 单个任务工作量不超过2人日
- 可独立验证和交付
- 有明确的完成标准
- 进度追踪
- 定期更新任务状态
- 按优先级调整任务顺序
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.
- 1mo ago First seen · 68 lines · 8 tokens per session scan A 145bdbaa7560
p-task-splitting is a cursor rule published in the GitHub repository xyzbit/AI-Coding (21 stars, last pushed 12mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 467 once invoked, about $0.0000 per session on Opus 5.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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.