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/xcodethink/open-claude-code-skills/17npx skills add xcodethink/open-claude-code-skills --skill 17git clone --depth 1 https://github.com/xcodethink/open-claude-code-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/xcodethink/open-claude-code-skills/17)<a href="https://agentmods.dev/skills/xcodethink/open-claude-code-skills/17"><img src="https://agentmods.dev/badge/skills/xcodethink/open-claude-code-skills/17.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.00199 | $0.02384 |
| Opus 5 | $0.00100 | $0.01192 |
| Sonnet 5 | $0.00040 | $0.00477 |
| Haiku 4.5 | $0.00020 | $0.00238 |
Grade A, and why
17-项目目录标准 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
项目目录结构标准
通用 skill — 所有新项目（SaaS / 工具 / 内部系统 / 实验项目）按本标准建立目录结构。 与 18-Git仓与安全 配套使用。
何时应用
- 新项目初始化时（创建仓库前必读）
- 老项目整理 cleanup 时
- 添加新文档分类时（确认是否进现有 10 大类还是新建）
顶层结构（强制）
project-root/
├── README.md 入口 — 一句话定位 + 导航 + 状态
├── CHANGELOG.md 发布日志（Keep a Changelog 格式）
├── CLAUDE.md 项目级 AI 协作规范
├── LICENSE 如适用（闭源项目可省）
├── .gitignore 根级 gitignore（参考 18-Git 规范模板）
├── .editorconfig 编辑器统一配置
│
├── apps/ 业务代码（client / server / mobile / extension）
├── packages/ 共享代码（types / utils / ui，可选）
├── infra/ 基础设施（Docker / K8s / Terraform / CI 配置）
├── scripts/ 工具脚本（含 promote.sh）
│
├── docs/ 全部业务/产品/运营文档（10 大分类，见下）
│
└── archive/ 项目级整体归档（旧版本/已废弃模块）
单 app 的简化版（早期 0-1 项目可省 apps/）：
project-root/
├── client/ 平铺
├── server/
├── docs/
└── ...
团队规模 > 3 人 或 子项目 ≥ 3 个时必须升级到
apps/结构。
docs/ 10 大分类（标准）
| # | 目录 | 中文术语 | 内容 | 更新频率 | 默认 classification |
|---|---|---|---|---|---|
| 00 | glossary.md（文件，非目录） |
术语 | 术语 + 跨域资源索引 | 持续 | L0-L1 |
| 01 | 01-strategy/ |
战略层 | vision / business model / 5 期演进 / tech architecture / north star metrics | 季度 review | L1 |
| 02 | 02-planning/ |
规划资料 | roadmap / phase-1/2/3 / OKR / milestones / 验收标准 | 阶段 review | L1 |
| 03 | 03-research/ |
参考资料 | competitors / industry / customer interviews / benchmarks | 持续累积 | L2 |
| 04 | 04-decisions/ |
思考资料 | ADRs / 决策记录 / pending / retros / hypothesis log | 事件驱动 | L2 |
| 05 | 05-product/ |
产品规划 | PRDs / specs / wireframes / 用户研究 | 每个 feature | L0-L1 |
| 06 | 06-engineering/ |
工程规范 | architecture / API spec / runbooks / postmortems / coding-standards | 每月 review | L0-L1 |
| 07 | 07-marketing/ |
市场规划 | brand / messaging / GTM / launch / content-calendar / channels | 月度 | L0-L1 |
| 08 | 08-operations/ |
运营规划 | team / hiring / finance / compliance / vendors / support SOP | 月度 | L2 |
| 09 | 09-investor/ |
投资人 | pitch-deck / data-room / cap-table / 月报 | 融资节奏 | L3 — 不进 git |
| 99 | 99-archive/ |
归档 | 已废弃版本，按 YYYY-MM-DD-描述/ 子目录 |
不删除 | 跟原文档同级 |
What ships with it
2 files 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.
- 4d ago First seen · 166 lines · 199 tokens per session scan A 118a714fd292
17-项目目录标准 is a skill published in the GitHub repository xcodethink/open-claude-code-skills (2 stars, last pushed 29d ago), licensed MIT. It adds 199 tokens to every session and 2,384 once invoked, about $0.0010 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-31.
Other skills, from other repositories
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
agent-phase-closeout
中文阶段收尾技能。用于完成一个阶段、准备开新对话、需要更新状态快照、冻结模块、整理已完成任务和下一步任务时。触发语包括"阶段收尾""帮我收工""准备开新对话""更新快照""冻结阶段""总结当前状态"。.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
moai-workflow-project
Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Absorbed from moai-workflow-templates, moai-docs-generation, and moai-workflow-jit-docs.
project-plan
Turn a product goal or feature request into a clear Agiflow project plan with small, testable tasks in Planning status. Use when starting a project, decomposing a feature, clarifying requirements, or converting an idea into an actionable backlog.
refine-task
Refine an existing Agiflow task into an unambiguous, testable specification without expanding its intended outcome. Use when a task is vague, lacks acceptance criteria, has unclear scope or dependencies, or is not ready for backlog grooming.