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/geminilight/mindos/project-wikinpx skills add GeminiLight/MindOS --skill project-wikigit clone --depth 1 https://github.com/GeminiLight/MindOSWrote 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/geminilight/mindos/project-wiki)<a href="https://agentmods.dev/skills/geminilight/mindos/project-wiki"><img src="https://agentmods.dev/badge/skills/geminilight/mindos/project-wiki.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.00063 | $0.06663 |
| Opus 5 | $0.00032 | $0.03331 |
| Sonnet 5 | $0.00013 | $0.01333 |
| Haiku 4.5 | $0.00006 | $0.00666 |
Grade A, and why
project-wiki 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 — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Wiki Skill
为 Vibe Coding 项目(人类描述意图,Agent 写代码)生成和维护结构化 wiki。wiki 是 Agent 的输入物料,直接决定输出质量。
执行流程
初始化(wiki/ 不存在或为空)
- 扫描
wiki/目录,列出已有文件 - 对照必要文件清单(见下方"文件体系"),识别缺失项
- 与用户确认将要创建的文件列表
- 生成骨架:从本 Skill 的
assets/目录读取对应模板,填入用户上下文(不确定的部分留<!-- TODO: ... -->占位) - 更新导航:如已有
01-project-roadmap.md,追加新阶段索引行 - 标记新鲜度:每个生成的文件头部加
<!-- Last verified: YYYY-MM-DD | Current stage: X --> - 注入维护规则:将下方"日常维护规则"章节的内容追加到项目
CLAUDE.md(已有则合并差异,不替换整个文件)。这一步不能跳过——wiki 的日常同步依赖这些规则写入 CLAUDE.md
重构 / 更新(wiki/ 已有文件)
- 扫描
wiki/下所有文件和子目录,检查编号方案(紧凑 or 展开)、新鲜度标记 - 诊断:
- 缺编号前缀?信息重叠?已完结 stage 未归档?内容与代码不一致?
- 膨胀检测:stage 文件超 300 行、其他文件超 500 行 → 建议拆分
- 散落文件:wiki 根目录中不属于任何编号区段的文件(如
ui-audit-*.md)→ 建议归入合适的子目录(reviews/)或运维区段(8x) - 命名一致性:
specs/下混有task-spec-*和spec-*→ 不强制迁移,但新建一律用spec-*;spec 散落在 wiki 根目录 → 建议迁入specs/ - 自定义子目录:识别
plugins/、images/等项目特有目录,标记为已知自定义目录,不报为异常
- 生成改动清单(重命名 / 合并 / 拆分 / 归档 / 迁移 / 更新内容),与用户确认
- 执行改动
- 验证一致性:文件间引用链接有效、roadmap 索引与实际文件对应
- 检查维护规则:确认项目
CLAUDE.md中已有 wiki 维护规则,缺失则追加(不替换整个文件)
文件体系
编号体系
编号按**"战略 → 架构 → 规范 → 阶段 → 运维 → 日志"**分层。根据项目规模选择紧凑或展开方案:
紧凑方案(≤5 个 stage,适合多数项目):
wiki/
├── 00-product-proposal.md
├── 01-project-roadmap.md
├── 02-system-architecture.md # 紧凑方案用 0x 统一放战略+架构
├── 03-design-principle.md
├── 04-api-reference.md
├── 1x 阶段 Stages
│ ├── 10-stage-a.md
│ ├── 11-stage-b.md ...
├── 80-known-pitfalls.md
├── 85-backlog.md
├── 90-changelog.md
├── specs/ · refs/ · reviews/ · archive/
展开方案(>5 个 stage 或需要更多分层空间):
wiki/
├── 0x 战略 Strategy — 全局视角
│ ├── 00-product-proposal.md
│ ├── 01-project-roadmap.md
│ ├── 02-business-model.md
│ └── 03-technical-pillars.md
├── 2x 架构 Architecture — 系统是怎么建的
│ ├── 20-system-architecture.md
│ └── 21-design-principle.md
├── 3x 接口 API
│ └── 30-api-reference.md
├── 4x 规范 Conventions
│ ├── 40-conventions.md
│ └── 41-dev-pitfall-patterns.md
├── 6x 阶段 Stages — 各阶段详细 spec
│ ├── 60-stage-a.md ...
├── 8x 运维 Operations
│ ├── 80-known-pitfalls.md
│ ├── 81-postmortem-*.md
│ ├── 84-design-exploration.md
│ └── 85-backlog.md
├── 9x 日志 Log
│ └── 90-changelog.md
├── specs/ · refs/ · reviews/ · archive/
What ships with it
19 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.
- assets/api-reference.tmpl.md 881 B
- assets/backlog.tmpl.md 231 B
- assets/changelog.tmpl.md 261 B
- assets/conventions.tmpl.md 808 B
- assets/design-exploration.tmpl.md 622 B
- assets/design-principle.tmpl.md 1.2 KB
- assets/development-guide.tmpl.md 534 B
- assets/glossary.tmpl.md 287 B
- assets/known-pitfalls.tmpl.md 372 B
- assets/postmortem.tmpl.md 997 B
- assets/product-proposal.tmpl.md 1.2 KB
- assets/project-roadmap.tmpl.md 559 B
- assets/ref.tmpl.md 663 B
- assets/review.tmpl.md 508 B
- assets/spec.tmpl.md 735 B
- assets/stage-x.tmpl.md 1.4 KB
- assets/system-architecture.tmpl.md 1.2 KB
- references/file-reference.md 14 KB
- references/writing-guide.md 1008 B
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 · 436 lines · 63 tokens per session scan A 35b6caa363de
project-wiki is a skill published in the GitHub repository GeminiLight/MindOS (664 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 6,663 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
acontext-installer
Install Acontext, Login & Init Acontext Project, Add Skill Memory to Agent.
core
Use when knowledge base hub — PARA-structured company memory combining company-kb and kb for persistent context, project documentation, and agent recall across sessions. Use when working with knowledge base, company knowledge, or persistent memory.
kb-memory
Use when knowledge base and memory system for AI agents. Covers company KB, persistent memory, session recall, and brain architecture for context preservation.
Skill Creator
Guide for creating effective Elephant Agent skills. Use this skill when users want to create a new skill or update an existing skill that extends Elephant Agent with specialized knowledge, workflows, or tool integrations.
wegent-knowledge
Knowledge base management and search tools for Wegent. Provides capabilities to list, create, update, and search knowledge bases and documents using RAG retrieval. Use this skill when the user wants to manage knowledge bases, documents, or search for information programmatically.
openlore
Query and publish to an OpenLore knowledge base over SSH using ordinary shell commands. Use when a task needs project documentation, runbooks, shared team knowledge, or a place to publish findings.