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 cognitive-version-snapshotgit 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/cognitive-version-snapshot)<a href="https://agentmods.dev/skills/tashangkd/tashan-cursor-skills/cognitive-version-snapshot"><img src="https://agentmods.dev/badge/skills/tashangkd/tashan-cursor-skills/cognitive-version-snapshot/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/cognitive-version-snapshot"><img src="https://agentmods.dev/badge/skills/tashangkd/tashan-cursor-skills/cognitive-version-snapshot.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.00063 | $0.01043 |
| Opus 5 | $0.00032 | $0.00522 |
| Sonnet 5 | $0.00013 | $0.00209 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
cognitive-version-snapshot 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cognitive-version-snapshot — 100% identical, 2 lines differ
What it actually says
版本快照 Skill（Cognitive Version Snapshot）
当L1文档发生重大变更时，创建新的 x.0 版本快照，作为后续变更的新基准。 基于
维护协议_自洽规范.md第0.2条：版本快照+变更日志体系。
何时使用本 Skill（vs 普通修改）
| 修改类型 | 处理方式 |
|---|---|
| 补充一个段落/修改措辞 | 直接修改 + 在变更记录追加一条 |
| 增加一个新章节 | 直接修改 + 在变更记录追加一条 |
| 核心论点发生变化 | 触发本 Skill，创建 v2.0 快照 |
| 文档结构大幅重组 | 触发本 Skill，创建 v2.0 快照 |
| 从根本上更新了主题定位 | 触发本 Skill，创建 v2.0 快照 |
激活后执行
Step 1 确认目标文档和版本号
→ 读取 历史版本/ 目录，找到最新的 vN.0 快照
→ 新版本号 = v(N+1).0
Step 2 对比当前版本与最近 vN.0 快照的差异
→ 确认差异确实构成「重大变更」（满足上表中的标准）
→ 如果只是增量修改，提示用户直接修改+变更记录即可
Step 3 创建新的 x.0 快照
→ Copy: [文档名].md → 历史版本/[文档名]_v(N+1).0_YYYYMMDD.md
→ 告知用户：「✅ 已创建 v(N+1).0 快照」
Step 4 在变更记录文件中追加里程碑条目
→ Write to [文档名]_变更记录.md（追加）：
## v(N+1).0 里程碑（YYYY-MM-DD）
**变更性质**：[核心论点变化/结构重组/定位更新]
**主要变更**：[一段话描述与 vN.0 的核心差异]
**快照路径**：历史版本/[文档名]_v(N+1).0_YYYYMMDD.md
**触发原因**：[什么事件/对话触发了这次重大变更]
Step 5 追加系统日志
[LOG-YYYYMMDD-NN] cognitive-version-snapshot | [文档名] 创建v(N+1).0快照 | [变更性质]
版本历史格式示例
在变更记录文件中，版本历史应该像这样：
## v1.0 基准（2026-03-19）
[2026-03-19] [create] 全文 | 初次迁入认知结构 | 系统性整理
快照：历史版本/[文档名]_v1.0_20260319.md
---
[2026-03-20] [supplement] 第三章 | 补充OPC社区相关论述 | 对话触发
[2026-03-21] [revise] 第一章第二节 | 修订马斯洛层次的表述 | 矛盾消解
---
## v2.0 里程碑（2026-03-25）
**变更性质**：核心论点变化
**主要变更**：从「三类问题框架」扩展为「五类问题框架」，认知科学基础单独成维度
**快照路径**：历史版本/[文档名]_v2.0_20260325.md
**触发原因**：与郑总深入讨论认知科学后，原有框架无法容纳新的洞见
---
[2026-03-26] [supplement] 第五章 | 新增认知科学基础维度详细论述 | v2.0后补充
注意事项
- 不要创建过多版本快照：不是每次修改都要打 x.0，只有真正的「里程碑」才打
- 版本快照是不可变的：创建后不要修改快照文件，它是历史记录
- 变更记录是追加的：只允许追加，不允许修改历史条目
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.
- 7d ago First seen · 90 lines · 63 tokens per session scan A 2e96b66cfbbd
cognitive-version-snapshot is a skill published in the GitHub repository TashanGKD/tashan-cursor-skills (20 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 1,043 once invoked, about $0.0003 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
ship
Release engineer execution mode. Handles git operations, runs tests, creates PRs. Use when user says /ship, wants to commit and push, needs to create a PR, or is ready to land their changes.
github-repo-triage
Triage and maintain GitHub repositories — assess open issues/PRs, cherry-pick contributions, manage releases, and publish packages. Use when the user wants to catch up on a repo, review open issues, merge community PRs, cut a release, or publish to package registries.
gh-cli
Interact with GitHub via the gh CLI for PRs, issues, releases, Actions, and API calls. Use when performing any GitHub operation such as creating PRs, viewing issues, checking CI status, making API requests, or managing releases.
ship
Enter the Ship phase of CocoBrew. Reads review.md approval, generates structured commit, creates semantic version tag, optionally creates PR via gh CLI, and records deployment details. Requires approved review.
release-branch
Make the merge/PR/keep/discard decision for a feature branch, verify coverage gates, create the PR with gh, and clean up the worktree. Use when a feature is done and ready to ship, or when user says "release", "merge", or "open a PR".
publish-package
Package registry publishing for npm, crates.io, PyPI, and Homebrew. Verifies prerequisites, runs the publish command, confirms success, and surfaces actionable error hints on failure.