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 skill-evolution-planner-metagit 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/skill-evolution-planner-meta)<a href="https://agentmods.dev/skills/tashangkd/tashan-cursor-skills/skill-evolution-planner-meta"><img src="https://agentmods.dev/badge/skills/tashangkd/tashan-cursor-skills/skill-evolution-planner-meta/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/skill-evolution-planner-meta"><img src="https://agentmods.dev/badge/skills/tashangkd/tashan-cursor-skills/skill-evolution-planner-meta.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.00153 | $0.02116 |
| Opus 5 | $0.00077 | $0.01058 |
| Sonnet 5 | $0.00031 | $0.00423 |
| Haiku 4.5 | $0.00015 | $0.00212 |
Grade A, and why
skill-evolution-planner-meta 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 9d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 体系演进规划（skill-evolution-planner-meta）
对应关系：
- product-evolution-planner → 对照产品原则，主动规划产品演进
- skill-evolution-planner-meta → 对照积累的模式，主动规划 Skill 体系演进
强绑定 Rule：R2 NO_FABRICATION / R3 READ_FIRST / R1 EVIDENCE_FIRST / R6 ARTIFACT_FIRST
知识导航表（执行前必须理解的概念根）
| 层级 | 文档 | 需要理解的概念 |
|---|---|---|
| D0 认知根（必读） | _内部总控/认知结构/L1_系统性文档/系统架构思维维度/自进化智能体系统形式规范_v1.0.md |
层2：自进化定义（系统能检测并消除自身Gap）；层5：G（间隙感知）→M（变更引擎）→R（注册表）完整闭环 |
| D3 规范参考 | _内部总控/认知结构/L1_系统性文档/系统架构思维维度/Skill体系设计原则_v1.0.md |
§1 唯一最终原则（自我进化能力）；§2.5 三型统一决策树 |
| D4 运行时数据 | .cursor/skills/skill-index/PENDING-EXPERIENCES.md + CO-BUILD-LOG.md + PENDING-SKILLS.md + SYSTEM-BLUEPRINT.md |
G缓冲区（已积累的Gap信号）+ 需求积压 + 体系蓝图 |
核心概念速查： ① 演进规划 = S4层智能（环境感知+战略分析），不是修复现有Gap而是规划未来的Gap ② 证据驱动：每条建议必须引用≥2次历史记录（CO-BUILD-LOG或PENDING-EXPERIENCES） ③ 输出必须是正式文件（R6 ARTIFACT_FIRST）：skill-evolution-plan-YYYYMMDD.md
激活后立即执行
Step 1 读取 Skill 体系的历史积累数据（R3 READ_FIRST）
用 explore 子智能体并行读取：
- .cursor/skills/skill-index/CO-BUILD-LOG.md（决策轨迹，过程层）
- .cursor/skills/skill-index/PENDING-EXPERIENCES.md（踩坑模式，结果层）
- .cursor/skills/skill-index/PENDING-SKILLS.md（需求积压）
- .cursor/skills/skill-index/SYSTEM-BLUEPRINT.md（体系蓝图）
- .cursor/skills/skill-index/SKILL-INDEX.md（当前状态）
若某个文件不存在，跳过并在报告中标注「未找到」。
Step 2 从五个维度分析演进方向（R1 EVIDENCE_FIRST：每条必须引用具体数据来源）
【维度1：重复模式 → 候选新 Skill】
分析 PENDING-EXPERIENCES 和 CO-BUILD-LOG：
→ 哪类「踩坑/新发现」反复出现（≥2次）但没有对应 Skill？
→ CO-BUILD-LOG 中有没有「缺失 Skill」类型（E 类）的重复记录？
→ 这些模式是否已在 PENDING-SKILLS 中？若没有，应该加入。
【维度2：架构压力 → 候选重构】
分析 CO-BUILD-LOG 中的「转折/方向调整」（III 类条目）：
→ 哪些转折揭示了当前 Skill 体系的架构缺陷（不只是单个 Skill 的问题）？
→ 有没有多个 Skill 因相似原因被修改，暗示应该合并或提取公共机制？
→ 触发词体系是否已经变得复杂到用户难以记忆？
【维度3：PENDING-SKILLS 优先级校准】
→ 当前 PENDING-SKILLS 的优先级排序是否仍然合理？
→ 有没有本来是 P0 但因为新情况变成了不那么紧急的项？
→ 有没有新出现的需求比现有 P0 更紧急？
【维度4：SYSTEM-BLUEPRINT 准确性】
→ SYSTEM-BLUEPRINT.md 描述的任务类型清单是否仍然准确？
→ 有没有新的高频任务类型在蓝图中未被记录？
→ 子智能体编排方案是否需要更新？
【维度5：Skill 质量层次分析】
→ SKILL-INDEX 中有多少 Skill 仍为「🔵 待验证」状态？
→ CO-BUILD-LOG 或 PENDING-EXPERIENCES 中，哪些 Skill 出现了「✅ 验证通过」的记录？
→ 这些 Skill 可以升级为「✅ 已验证」
→ 哪些 Skill 的「🔵 待验证」状态持续存在，且从未在 CO-BUILD-LOG/PENDING-EXPERIENCES 中出现过？
→ 可能从未被使用，考虑合并或废弃
Step 3 生成演进建议清单
对每条建议：
- 建议标题（一句话）
- 数据来源（引用 CO-BUILD-LOG/PENDING-EXPERIENCES 的具体条目）
- 建议类型：新建/重构/合并/废弃/描述更新/触发词调整/架构升级
- 优先级：P0/P1/P2
- 路由：→ skill-designer Level 2/3 / skill-rule-修改规范 Level 1
Step 4 输出「Skill 体系演进建议报告」（R6：必须写文件）
写入：.cursor/skills/skill-index/skill-evolution-plan-YYYYMMDD.md
Step 5 路由询问
「📊 Skill 体系演进分析完成。共发现 N 条建议（P0: N，P1: N，P2: N）。
是否现在执行某项？
- 新建/重构 → 加载 skill-designer（Level 2/3）
- 修改描述/触发词 → 按 skill-rule-修改规范 Level 1
- 加入需求积压 → 更新 PENDING-SKILLS.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.
- 9d ago First seen · 156 lines · 153 tokens per session scan A f2f7b813062e
skill-evolution-planner-meta is a skill published in the GitHub repository TashanGKD/tashan-cursor-skills (20 stars, last pushed 5mo ago), licensed MIT. It adds 153 tokens to every session and 2,116 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
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…
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…