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-reconstructiongit 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-reconstruction)<a href="https://agentmods.dev/skills/tashangkd/tashan-cursor-skills/project-reconstruction"><img src="https://agentmods.dev/badge/skills/tashangkd/tashan-cursor-skills/project-reconstruction/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-reconstruction"><img src="https://agentmods.dev/badge/skills/tashangkd/tashan-cursor-skills/project-reconstruction.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.00159 | $0.03682 |
| Opus 5 | $0.00079 | $0.01841 |
| Sonnet 5 | $0.00032 | $0.00736 |
| Haiku 4.5 | $0.00016 | $0.00368 |
Grade A, and why
project-reconstruction 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.
How it starts
The opening of the file, as written. The whole thing — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
基于已有项目重构 Skill（project-reconstruction）
版本：v1.1 · 2026-03-23
适用场景：现有项目技术债积累严重，但 90% 业务逻辑是对的，只是放错了地方。 核心原则：迁移单位是「目录结构和模块边界」，不是重写业务逻辑。
关联角色：
- role-产品经理（Step 2：功能清单）
- role-技术架构师（Step 3：框架设计）
- role-审核者-系统破坏（Step 3.5：红蓝推演）
- skill-designer（Step 4：Cursor 规范配置）
知识导航表（激活前按顺序读取）
| 层级 | 文档 | 用途 |
|---|---|---|
| D0 | 现有项目的 产品经理/产品定义.md |
了解当前产品是什么 |
| D1 | 现有项目的 产品经理/开发计划.md |
了解哪些功能已实现 |
| D2 | 现有项目的 技术架构师/*.md（若有） |
了解现有技术积累 |
| D3 | _内部总控/认知结构/L1_系统性文档/系统架构思维维度/ |
架构设计的认知根 |
激活后立即执行
Step 0：评估是否适合重构（而非增量整改）
与用户确认以下判断（全部 Yes 才进入重构流程）：
□ 现有项目的技术债是「结构性的」（不是几个 Bug），改一个地方要追 3-5 个依赖方？
□ 业务逻辑大体正确，问题主要在「东西放错了地方」？
□ 可以接受约 1-2 周的迁移期（新旧项目并行）？
□ 核心数据（DB/文件系统）可以无损迁移？
若有 No → 评估增量整改是否更合适，向用户说明。 若全部 Yes → 继续 Step 1。
Step 1：新建项目文件夹 + 规范结构
在 项目群/ 下新建：{新项目名}/
├── 0_迁移决策/
│ └── 重构决策.md ← Step 1 完成后写入
├── 1_产品定义/
│ └── 功能清单.md ← Step 2 输出
├── 2_技术架构/
│ ├── 技术框架.md ← Step 3 输出
│ └── 红蓝推演.md ← Step 3.5 输出（必须回写到技术框架）
├── 3_开发计划/
│ └── 开发计划.md ← Step 5 输出
├── 开发规范.md ← Step 4 输出
└── README.md ← 阅读顺序说明
写入 0_迁移决策/重构决策.md，包含：
- 为什么选重构而非增量整改（具体原因，不是套话）
- 哪些代码直接 copy，哪些需要重写（按文件级估计）
- 数据迁移策略（DB/文件系统）
- 风险评估（功能遗漏风险 / 数据迁移风险 / API兼容风险）
Step 2：PM 视角——功能清单（角色：role-产品经理）
目标：让「怕遗漏」的风险变成可验证的清单
执行以下操作：
- 读取 D0（现有产品定义）和 D1（开发计划），提取所有功能
- 按功能域分组，为每个功能标注状态：
- ✅ 已实现且验证通过
- ⚠️ 已实现但有已知缺陷（记录缺陷描述）
- 🔄 正在开发中
- ⏳ 规划中（明确需求但未实现）
- ❌ 废弃（设计过但不再做）
- 为功能清单中每个功能分配优先级（P0/P1/P2/P3）
输出：1_产品定义/功能清单.md
验收：用户确认功能清单无遗漏（重点检查 ✅ 的功能是否都在新框架里有对应位置）
Step 3：技术架构师视角——新框架设计（角色：role-技术架构师）
目标：设计「第一天就是对的」的架构，然后把旧代码搬进来
执行顺序（不可跳过）：
3a. 第一性原理推导
先定义核心数据模型（不看旧代码），回答：
这个系统的核心实体是什么？它们之间是什么关系？
每个实体的生命周期是什么？谁拥有谁？
3b. 模块切片（从依赖关系推导，不从旧项目目录推导）
按 Slice 依赖层次从底向上设计：
Slice 1（最底层，无依赖）→ Slice 2 → ... → Slice N（最上层）
每个 Slice：
- 职责一句话
- 对外接口（输入/输出）
- 内部不对外暴露的内容
- 与其他 Slice 的依赖关系
3c. 目录结构（从切片推导，不从旧项目复制）
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.
- 8d ago First seen · 308 lines · 159 tokens per session scan A 9658bb83e337
project-reconstruction is a skill published in the GitHub repository TashanGKD/tashan-cursor-skills (20 stars, last pushed 5mo ago), licensed MIT. It adds 159 tokens to every session and 3,682 once invoked, about $0.0008 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.
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…
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-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-preflight
Final verification checklist to run before declaring Android work finished — build, both themes, string resources, lifecycle and leak risks, registered permissions and components, resource parity between values and values-night, and honest reporting of what was and was not verified. Use at the end of any feature, fix…
android-ui-theming
Rules for Android XML layouts, Material 3 components, semantic color tokens, light/dark theming, dimensions (sdp/ssp), string resources and localization, accessibility, and edge-to-edge insets. Use when creating or editing any layout, drawable, style, color, vector, or string resource, or when a screen must work in…