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 TashanGKD/tashan-cursor-skills --skill project-backloggit clone --depth 1 https://github.com/TashanGKD/tashan-cursor-skillsWrote 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/tashangkd/tashan-cursor-skills/project-backlog)<a href="https://agentmods.dev/skills/tashangkd/tashan-cursor-skills/project-backlog"><img src="https://agentmods.dev/badge/skills/tashangkd/tashan-cursor-skills/project-backlog/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/tashangkd/tashan-cursor-skills/project-backlog"><img src="https://agentmods.dev/badge/skills/tashangkd/tashan-cursor-skills/project-backlog.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.00173 | $0.06961 |
| Opus 5 | $0.00086 | $0.03481 |
| Sonnet 5 | $0.00035 | $0.01392 |
| Haiku 4.5 | $0.00017 | $0.00696 |
Grade A, and why
project-backlog 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 6d 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 — 461 lines — stays where its author put it; the contents beside it link to each section on GitHub.
项目待办管理器（project-backlog）
核心原则：文档即状态，不依赖 AI 记忆。 任何输入先存文档；执行状态写在文档里；进程中断后可从文档恢复，不丢失。
认知根
认知根：_内部总控/认知结构/L1_系统性文档/系统架构思维维度/Skill体系设计原则_v1.0.md
关联：「文档即状态」是本 Skill 的核心执行范式。
待办文档规范（项目待办.md）
位置：项目群/[项目名]/产品经理/项目待办.md
（优先用 project-config.md 中的 PATH_待办 字段覆盖）
标准格式：
# 项目待办
> 所有类型的输入先到这里。说「处理项目待办」可触发自动处理流程。
| ID | 类型 | 内容摘要 | 来源日期 | 优先级 | 状态 |
|----|------|---------|---------|--------|------|
| B-01 | Bug | [描述] | YYYY-MM-DD | P0/P1/P2 | 🔲 |
| F-01 | Feature | [描述] | YYYY-MM-DD | — | 🔲 |
| U-01 | UX | [描述] | YYYY-MM-DD | P1 | 🔲 |
| P-01 | 原则 | [描述] | YYYY-MM-DD | — | 🔲 |
| R-01 | 规范偏差 | [描述] | YYYY-MM-DD | — | 🔲 |
| D-01 | 设计建议 | [描述] | YYYY-MM-DD | — | 🔲 |
状态标记：🔲 待处理 / 🔄 处理中 / ✅ 已完成 / ❌ 执行失败 / ⏸️ 搁置（待决策）/ 📬 已移交
ID 前缀：B=Bug / F=Feature / U=UX / P=原则 / R=规范偏差 / D=设计建议 + 两位流水号
架构层标签（B-xx Bug 可选，AI 平台项目推荐填写）：
L0=部署模型 / L1=状态管理 / L2=并发模型 / L3=LLM调用 / L4=数据隔离 / L5=Agent框架 / L6=可观测 / L7=安全 / L8=性能 / L9=扩展 / FE=前端
示例：B-01 | Bug | [L1] 更新认知显示构建中 | ...
知识导航表（执行前读取）
| 层级 | 文档 | 读取目的 |
|---|---|---|
| D0 | .cursor/project-config.md（若存在） |
获取 PATH_待办 和 PATH_技术追踪台 |
| ① | _内部总控/元项目导航.md |
project-config 不存在时确认当前活跃项目 |
可用 Skill 速查表（P-2 生成激活命令时的唯一参考）
⚠️ 生成激活命令时必须参考此表，不得凭记忆猜测触发词
| 待办类型 | 触发词（【X】格式） | 对应 Skill | 该 Skill 处理什么 | 前置条件 |
|---|---|---|---|---|
| P-xx 原则类 | 【立原则】：[原则描述] |
engineering-principle-recorder | 新工程/执行原则录入到 Rule/Role Skill 执行层，并审计现有违规 | 无 |
| B-xx P0/P1 Bug（需立即修复） | 【修复循环】 |
bug-fix-loop-coordinator | 读技术追踪台，P0→P1 循环 TDD 修复，直至清零。⚠️ 需要 Bug 已在追踪台中（P-2-1 写入追踪台后再激活） | 技术追踪台已有条目 |
| B-xx P2 Bug（仅记录） | 【记录问题】[Bug描述] |
issue-tracker | 拆分并记录到产品/技术追踪台，不立即修复 | 无 |
| F-xx Feature（新功能需求） | 【协调者】：[需求描述 + 用户决策] |
role-产品开发协调者 | 判断任务类型并编排完整产品开发流水线（PM→关卡A→架构师→关卡B→开发→关卡C→DevOps） | 无 |
| U-xx UX 问题（体验问题） | 【协调者】：[UX问题 + 用户决策] |
role-产品开发协调者 | 同上，协调者判断走产品修复还是前端/UI修复 | 无 |
| R-xx 规范偏差（已有规范被违反） | 【规范修复】：[规范偏差描述] |
project-convention-resolver | 接收–分类–路由–验证；已知规范的偏差修复（与「立原则」的区别：这里处理已有规范的违反，不是立新规范） | 无 |
| D-xx 设计建议（纳入迭代） | 【协调者】：评估设计建议：[描述] |
role-产品开发协调者 | 产品/技术层面评估并纳入开发计划 | 无 |
| D-xx 设计建议（仅存档） | 无需激活 Skill，project-backlog 直接写入 | — | 直接追加到技术架构.md「设计建议存档」节 | 技术架构.md 已存在 |
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.
- 6d ago First seen · 461 lines · 173 tokens per session scan A 8504c7a09fda
project-backlog is a skill published in the GitHub repository TashanGKD/tashan-cursor-skills (20 stars, last pushed 5mo ago), licensed MIT. It adds 173 tokens to every session and 6,961 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
team
Coordinate parallel work across multiple Cursor sessions via shared .omc/team/ state.
template-helpers
Catalog of the reusable building blocks shipped with this Android template — BaseActivity/BaseFragment, the helpers/ extension files (navigation, lifecycle, toast, snackbar, dialogs, images, permissions, theme, locale, settings intents, date, delay), common/ (Firebase, network, observers), and…
android-feature
Workflow for implementing a new Android feature, screen, fragment, activity, dialog, adapter, or enhancement in this XML/MVVM template. Use whenever the user asks to add, build, implement, or extend functionality — before writing any code. Covers planning, the MVVM/MVI skeleton, the Android configuration checklist…
android-new-project
Workflow for turning a fresh copy of this Android template into a new app — renaming the package/namespace/applicationId, branding (icons, splash, palette, fonts), Firebase setup, signing config, stripping unused sample screens, and verifying the foundation. Use when the user says they are starting a new app…
android-upgrade
Workflow for changing an existing working Android project — upgrading dependencies, AGP/Gradle or SDK levels, migrating deprecated APIs, refactoring, and fixing bugs, without breaking what already works. Covers baseline verification, scoping the diff, targetSdk behaviour changes, SharedPreferences/Room data…
android-build-config
Gradle and build configuration rules for this template — AGP 9 / Gradle 9 DSL (built-in Kotlin, compileSdk block, optimization block instead of minify/proguard), the gradle/libs.versions.toml version catalog, R8 keep rules in keepRules/.keep, gradle.properties defaults, and manifest registration. Use when editing…