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 skills/double-coding-lab/flow2spec/repo-dev-checknpx skills add double-coding-lab/Flow2Spec --skill repo-dev-checkgit clone --depth 1 https://github.com/double-coding-lab/Flow2SpecWhat 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.00089 | $0.01905 |
| Opus 5 | $0.00044 | $0.00953 |
| Sonnet 5 | $0.00018 | $0.00381 |
| Haiku 4.5 | $0.00009 | $0.00191 |
Grade A, and why
repo-dev-check 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 2d 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
2 near-identical copies found in the catalogue:
- repo-dev-check — 88% identical, 53 lines differ
- repo-dev-check — 88% identical, 53 lines differ
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repo-dev-check（本仓开发纪律自查）
适用：仅在 Flow2Spec 本仓自身开发时启用。下游项目不会拿到本 SKILL——它只存在于本仓的
.claude/skills/、.cursor/skills/、.codex/skills/,从不进templates/。单一事实源：本 SKILL 依据
f2s-dev-workflow-constraints规则执行（Claude：.claude/rules/repo-dev-workflow-constraints.md；Cursor：.cursor/rules/repo-dev-workflow-constraints.mdc；Codex：.codex/topics/repo-dev-workflow-constraints.md）。步骤 0 必须 Read 该规则全文。
触发场景
- 用户显式说「跑 dev-workflow 自查 / 检查是不是改错地方了」；
- 用户在 Flow2Spec 本仓内、Agent 即将提交前主动自查；
- Agent 发现自己刚做了配置根下的
Edit/Write，须补做本自查； - Agent 在改开发纪律相关的规则 / skill / topic 时（比如本文件、
f2s-dev-workflow-constraints）。
不触发：下游项目内、纯业务代码修改无 template/config-root 交集时。
前置
步骤 0：Read .claude/rules/repo-dev-workflow-constraints.md（Cursor：.cursor/rules/*.mdc；Codex：.codex/topics/*.md）全文。不 Read 直接开跑属违规。
编排
- 主 agent 通篇执行：本 skill 无重 IO 操作，无需拆子。
- 配置：不受
flow2spec.config.json.subAgent约束（无论 true / false 都主 agent 跑）。 - 写权：本 skill 不主动落盘业务文件；只做判定 + 建议；确实需要写盘时逐条回到具体 skill（如
f2s-git-commit）流程。
步骤
步骤 1：git 摸底
Bash：git status -s | grep -v DS_Store列出所有未提交改动。
步骤 2：写盘边界判定（对每份 pending 文件）
对步骤 1 列出的每一份改动文件，套下表判定：
| 文件路径模式 | 是否合规 | 判定依据 |
|---|---|---|
templates/zh-CN/** 或 templates/en-US/** |
✅ 合规 | 生产侧唯一入口 |
docs/** / lib/** / cli.js / scripts/** / package.json |
✅ 合规 | 包源码 |
.Knowledge/** |
✅ 合规 | 本仓自身知识库 |
.claude/rules/repo-dev-workflow-constraints.md |
✅ 合规 | 本仓专属手写规则（templates 无对应源） |
.claude/skills/repo-dev-check/** |
✅ 合规 | 本仓专属手写 skill（templates 无对应源） |
.cursor/rules/repo-dev-workflow-constraints.mdc |
✅ 合规 | 同上（Cursor 端） |
.cursor/skills/repo-dev-check/** |
✅ 合规 | 同上 |
.codex/topics/repo-dev-workflow-constraints.md |
✅ 合规 | 同上（Codex 端） |
.codex/skills/repo-dev-check/** |
✅ 合规 | 同上 |
.claude/rules/<其它>.md / .cursor/rules/<其它>.mdc / .codex/topics/<其它>.md |
❌ 违规 | 有 templates 对应源 → 应改 templates/{zh-CN,en-US}/rules/<其它>.md |
.claude/skills/<其它>/** / .cursor/skills/<其它>/** / .codex/skills/<其它>/** |
❌ 违规 | 有 templates 对应源 → 应改 templates/{zh-CN,en-US}/skills/<其它>/SKILL.md |
根 AGENTS.md |
❌ 违规 | 由 buildCodexAgentsMd(templatesDir, ...) 从 templates 拼装 → 应改 templates/{zh-CN,en-US}/AGENTS.md |
.claude/hooks/** / .cursor/hooks/** / .codex/hooks/** / .claude/settings.json / .cursor/hooks.json / .codex/hooks.json |
❌ 违规 | init 产物 → 需求要改的话改 lib/init.js 或 templates/ |
packages/core/templates/** |
❌ 违规 | 由 scripts/sync-core-templates.js 从根 templates/ 自动生成,已进 .gitignore → 想改模板应改根 templates/,同步靠脚本 |
.claude/memory/** / LOCAL_CONTEXT.md |
⚠️ 本地态 | 不入库，不受约束（但提醒别 commit） |
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.
- 2d ago First seen · 102 lines · 89 tokens per session scan A a6670c1d794f
repo-dev-check is a skill published in the GitHub repository double-coding-lab/Flow2Spec (47 stars, last pushed 5d ago), licensed MIT. It adds 89 tokens to every session and 1,905 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…