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 agentmods add instructions/linfee/spec-kit-cn/claude-mdgit clone --depth 1 https://github.com/Linfee/spec-kit-cnWrote 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/instructions/linfee/spec-kit-cn/claude-md)<a href="https://agentmods.dev/instructions/linfee/spec-kit-cn/claude-md"><img src="https://agentmods.dev/badge/instructions/linfee/spec-kit-cn/claude-md.svg" alt="Measured on agentmods" 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 | $0.03776 | $0.03776 |
| Opus 5 | $0.01888 | $0.01888 |
| Sonnet 5 | $0.00755 | $0.00755 |
| Haiku 4.5 | $0.00378 | $0.00378 |
Grade A, and why
spec-kit-cn CLAUDE.md 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 4d 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Kit CN
项目性质: GitHub Spec Kit 的官方中文复刻版本, 仅做中文本地化, 不开发新特性
项目标识
核心信息
- 项目名称: Spec Kit CN
- 原版项目: github/spec-kit
- 当前项目: linfee/spec-kit-cn
- 包名:
specify-cn(原版:specify-cli不做更改) - 命令:
specify-cn(原版:specify) - 文档语言: 中文(原版: 英文)
核心原则
- 功能对等: 与原版保持完全一致的功能, 不添加新特性
- 仅做本地化: 专注于中文翻译和本地化适配
- 同步优先: 定期与原版同步, 保持技术更新
关键差异
| 项目 | 原版 | 中文版 |
|---|---|---|
| 包名 | specify-cli |
specify-cn-cli |
| 命令 | specify |
specify-cn |
| 文档 | 英文 | 中文 |
| 功能 | 持续开发 | 仅做本地化 |
| 斜杠命令 | /speckit.plan |
保持一致 |
快速参考
常用命令
# 开发环境
uv sync # 同步依赖
uv run specify-cn --help # 运行 CLI
uv run specify-cn check # 检查工具链
# 测试功能
specify-cn init test-project --ai claude # 测试项目初始化
specify-cn --help | grep -E "中文|Spec Kit CN" # 验证中文输出
自动化翻译工作流
# 一键自动化翻译(推荐)
/translation-auto # 全自动翻译流程
# 原版更新处理
/translation-sync # 智能同步原版更新
# 质量管理
/translation-qa # 质量保证检查
/translation-fix # 智能修复问题
# 人工审核
/translation-review # 人工审核(已存在)
/translation-workflow # 工作流指南
项目目录结构
项目根目录/
├── src/specify_cli/ # 核心代码(必须同步)
├── templates/ # 模板文件(需要本地化)
├── scripts/ # 构建脚本(完全同步, 不翻译)
├── .devcontainer/ # 开发容器配置(完全同步, 不翻译)
├── .github/ # CI配置(谨慎同步, 不翻译)
├── docs/ # 项目文档(需要本地化)
├── memory/ # 项目章程(需要本地化)
├── spec-kit/ # 原版项目(.gitignore)
├── .claude/commands/ # 翻译自动化命令
├── TERMINOLOGY.md # 术语表
├── TRANSLATION_STANDARDS.md # 翻译标准
├── CHANGELOG.md # 版本记录(独立维护)
└── CLAUDE.md # 项目记忆文件
文件分类与处理策略
| 类别 | 目录/文件 | 同步策略 | 本地化策略 |
|---|---|---|---|
| 核心代码 | src/specify_cli/ |
必须同步 | CLI输出信息需要中文 |
| 模板系统 | templates/ |
结构同步 | 完全中文翻译 |
| 构建脚本 | scripts/ |
完全同步 | 不翻译 |
| 开发环境 | .devcontainer/ |
完全同步 | 不翻译 |
| CI配置 | .github/ |
谨慎同步 | 不翻译 |
| 项目文档 | docs/, README.md |
结构参考 | 完全中文翻译 |
| 项目章程 | memory/constitution.md |
结构同步 | 完全中文翻译 |
| 原版追踪 | spec-kit/ |
不提交 | 不适用 |
| Agent入口 | AGENTS.md |
独立维护 | 引用CLAUDE.md |
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.
- 4d ago First seen · 324 lines · 3,776 tokens per session scan A ab9da85acc51
spec-kit-cn CLAUDE.md is an instructions file published in the GitHub repository Linfee/spec-kit-cn (695 stars, last pushed 1mo ago), licensed MIT. It adds 3,776 tokens to every session, about $0.0189 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-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.