Borrowing it
Nothing to install: this file belongs to Peiiii/nextclaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Peiiii/nextclaw/master/.agents/wiki/skills/governance/file-organization-governance/SKILL.mdgit clone --depth 1 https://github.com/Peiiii/nextclawWrote 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/peiiii/nextclaw/file-organization-governance)<a href="https://agentmods.dev/skills/peiiii/nextclaw/file-organization-governance"><img src="https://agentmods.dev/badge/skills/peiiii/nextclaw/file-organization-governance/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/peiiii/nextclaw/file-organization-governance"><img src="https://agentmods.dev/badge/skills/peiiii/nextclaw/file-organization-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00070 | $0.00594 |
| Opus 5 | $0.00035 | $0.00297 |
| Sonnet 5 | $0.00014 | $0.00119 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
file-organization-governance 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 11d 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.
What it actually says
文件组织治理
入口判断
先选择一个当前模式，不批量读取全部参考：
- 新增/重命名/移动文件、角色后缀或 kebab-case：读取 命名合同；完整规格仅在规则歧义时再读 命名规格。
- 判断 service/store/utils/config/types、假角色或 barrel：读取 文件角色。
- 判断单 feature root、features、shared、contributions、跨包公共入口：读取 Feature Root。
- 用户只要目录热点、问题量化和治理优先级：读取 目录概况，不直接重构。
同一决策只读取一个模式；只有前一模式明确暴露另一个独立问题时才继续。
共同规则
- 先角色、再领域、再层级；没有真实复杂度不展开模板目录。
- 文件名表达主要职责，目录和后缀一致；禁止
common/misc/general等模糊垃圾桶。 - 角色冲突检查只提出问题，不预设修复方向：必须同时评估“增强实现以成为真实角色 owner”和“按现状改名/移动”两个候选，比较职责收益、状态与生命周期封装、复用与测试价值、调用方成本和新增抽象负担；禁止默认选择改动最小的一边。
- 一个 feature root 内优先内聚；只有稳定跨 feature 复用才进入 shared。
- 跨 workspace 依赖只走公共入口或 exports，不用消费者 alias 绕过边界。
- 新增、重命名、移动或角色边界变化前运行
pnpm preflight:governance -- <planned-paths...>。 - 局部修改现有文件不重复运行 planned-path preflight，也不加载本 skill。
自动检查
现有目录扫描与重构脚本位于 scripts/。脚本结果是结构事实信号，不替代 role/feature owner 判断，也不能决定是升级实现还是修正命名；自动改写前先确认范围且不得触碰无关 WIP。
输出
说明当前模式、目标路径、角色/feature 判断、preflight 结果和明确不改的范围。不要同时复述四份 reference。
What ships with it
9 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.
- demo.md 1.3 KB
- references/feature-root.md 5.8 KB
- references/file-naming-spec.md 4.9 KB
- references/file-roles.md 8.9 KB
- references/naming.md 5.8 KB
- references/overview.md 7.2 KB
- scripts/check-organization.js 3.2 KB runs code
- scripts/enhanced-check-organization.js 6.2 KB runs code
- scripts/refactor-organization.js 1.3 KB runs code
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.
- 11d ago First seen · 36 lines · 70 tokens per session scan A a1763b5ae97f
file-organization-governance is a skill published in the GitHub repository Peiiii/nextclaw (256 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 594 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-08-30.
Other skills, from other repositories
openclaw-github-dedupe
Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions. Supports autonomous mode for provided-link-only closeout, merge/fix follow-through, changelog, and post-merge issue/PR cleanup.
openclaw-pr-batch-sweep
Select, review, repair, validate, and land batches of up to 20 low-risk OpenClaw contributor pull requests using Vincent's maintainer preferences and bounded sub-agent lanes. Use for "next 20", broad contributor PR sweeps, merge-candidate mining, or continued PR-batch work where drafts, maintainer work, trivial…
tmux-lane-orchestrator
Manage one tmux agent lane from its matching ops pane, inspect live pane state and Codex logs on cold start, and produce concise manager summaries for OpenClaw and adjacent project work.
ghcrawl-cluster-operator
Use when inspecting a ghcrawl SQLite store, pulling GitHub issue/PR data, refreshing summaries, embeddings, and clusters, or extracting one cluster and its evidence through the ghcrawl CLI.
opik-optimizer
Optimize LLM prompts, tools, and agents in Opik using standardized optimizer workflows (prompt optimization, tool optimization, and parameter tuning), dataset/metric wiring, and result interpretation.
org-branch-cleanup
Audit and safely prune stale branches across a GitHub organization with immutable snapshots, conservative merged-PR classification, live SHA/protection/open-PR revalidation, resumable deletion ledgers, and post-delete verification. Use when a maintainer asks to clean up old, dead, merged, bot-created, or abandoned…