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.
git clone --depth 1 https://github.com/Claudate/project-multilevel-indexWrote 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/commands/claudate/project-multilevel-index/check-index)<a href="https://agentmods.dev/commands/claudate/project-multilevel-index/check-index"><img src="https://agentmods.dev/badge/commands/claudate/project-multilevel-index/check-index/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/commands/claudate/project-multilevel-index/check-index"><img src="https://agentmods.dev/badge/commands/claudate/project-multilevel-index/check-index.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01401 |
| Opus 5 | $0.00000 | $0.00700 |
| Sonnet 5 | $0.00000 | $0.00280 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
check-index 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 9d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
命令: /check-index - 一致性检查
🎯 使用场景
验证索引系统的完整性和一致性,发现潜在问题。
📋 执行步骤
步骤 0: 加载语言配置
必须首先执行,详见 ../core/i18n.md
步骤 1: 检查文件头完整性
输出: {{LANG.messages.commands.checkIndex.checking}}
扫描所有代码文件,验证是否包含完整的文件头注释。
检查项:
- 是否有注释块
- 是否包含
Input:字段 - 是否包含
Output:字段 - 是否包含
Pos:字段
统计结果:
{{LANG.messages.commands.checkIndex.fileHeaderIntegrity}}:
- {{LANG.messages.commands.checkIndex.allGood}} # 全部正常
或
- {{LANG.messages.commands.checkIndex.missing}} # 替换 {count}
- 列出缺失的文件路径
步骤 2: 检查文件夹索引
对每个包含代码文件的文件夹:
检查项:
- 是否存在
FOLDER_INDEX.md - 索引中列出的文件是否都存在
- 是否有文件未被索引(新增文件)
- 自指声明是否存在
统计结果:
{{LANG.messages.commands.checkIndex.folderIndex}}:
- ✅ {count}/{total} 正常
- ⚠️ 缺失的索引: 列出路径
- ⚠️ 过期的条目: 列出不存在的文件
步骤 3: 检查依赖关系
分析所有文件的 import 语句:
检查项:
-
循环依赖检测:
- 构建依赖图
- 使用深度优先搜索(DFS)检测环
- 列出所有循环依赖链
-
断链检测:
- 验证被依赖的文件是否存在
- 列出找不到的依赖
统计结果:
{{LANG.messages.commands.checkIndex.dependencies}}:
- ✅ 无循环依赖
或
- {{LANG.messages.commands.checkIndex.circularDep}} # 替换 {count}
- 列出循环: A → B → C → A
- ⚠️ 断链依赖: 列出找不到的文件
步骤 4: 检查索引结构
验证整体结构:
检查项:
PROJECT_INDEX.md是否存在于根目录- 依赖关系图是否有效(Mermaid 语法)
- 所有 FOLDER_INDEX.md 是否被 PROJECT_INDEX.md 引用
步骤 5: 生成报告
输出: {{LANG.messages.commands.checkIndex.title}}
完整报告格式:
{{LANG.messages.commands.checkIndex.title}}
===================
{{LANG.messages.commands.checkIndex.fileHeaderIntegrity}}: 55/57
- src/utils/legacy.js
- src/temp/test.ts
{{LANG.messages.commands.checkIndex.folderIndex}}: 8/8 ✅
{{LANG.messages.commands.checkIndex.dependencies}}:
⚠️ {{LANG.messages.commands.checkIndex.circularDep}} # {count} = 1
- src/a.ts → src/b.ts → src/c.ts → src/a.ts
{{LANG.messages.commands.checkIndex.structure}}: ✅
{{LANG.messages.commands.checkIndex.suggestions}}:
1. {{LANG.messages.commands.checkIndex.runUpdate}}
2. {{LANG.messages.errors.circularDep}}
如果一切正常:
{{LANG.messages.commands.checkIndex.perfect}}
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.
- 9d ago First seen · 229 lines · 0 tokens per session scan A 75afb4c49694
check-index is a command published in the GitHub repository Claudate/project-multilevel-index (139 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,401 tokens. 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 commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.