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 skills add zuoyebang/aiweave --skill update-indexgit clone --depth 1 https://github.com/zuoyebang/aiweaveWrote 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/zuoyebang/aiweave/update-index)<a href="https://agentmods.dev/skills/zuoyebang/aiweave/update-index"><img src="https://agentmods.dev/badge/skills/zuoyebang/aiweave/update-index.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.1 | $0.00030 | $0.00661 |
| Opus 5 | $0.00015 | $0.00331 |
| Sonnet 5 | $0.00006 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
update-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 8d 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
自动扫描 docs/ 目录，对比 INDEX.md，更新计数和条目。模式：$ARGUMENTS（空则更新，dry-run 则仅报告）。
公共步骤模板见 skills-spec/01_skill_authoring_guide.md §A-§E。本 Skill 不生成代码，故第 5 步测试同步不适用。
第 0 步：前置检查
无 🚫 模块拒绝规则。仅需确认 docs/INDEX.md 存在。
第 1 步：扫描实际文档
按 docs/ 子目录依次扫描：
docs/architecture/*.md→ 列出所有文件docs/api/*.md→ 统计每个文件中接口数docs/service/*.md→ 列出所有docs/schema/*.md→ 统计 DDL 中表数docs/cache/*.md→ 列出docs/circuit_breaker/*.md→ 列出docs/testing/*.md→ 列出- 检查是否有新顶层目录
第 2 步：生成差异报告
=== INDEX.md 差异报告 ===
📝 architecture/ — 条目变更
+ new_doc.md（新增）
- removed_doc.md（已删除）
📊 api/ — 计数变更
audience_a_interfaces：5（无变化）
audience_b_interfaces：23 → 24（变更）
🆕 新目录（无）
第 3 步：执行更新（非 dry-run 模式）
- 新增文件：在对应表格新增行，说明文字取 md 第一个
#标题 - 删除文件：从表格移除
- 更新接口数 / 表数 / 任务数等
- 发现新顶层目录 → 询问用户说明后再添加
第 4 步：文档同步（公共项见 §C）
- 重新扫描一次，确认差异报告为空
- 回复末尾声明：「文档同步：更新了
docs/INDEX.md」
第 5 步：测试同步
不适用——本 Skill 不生成业务代码。
第 6 步：验证
差异报告归零即为通过。
注意事项
- 不修改已有条目说明文字，除非文件被删除/重命名
- 保持表格格式一致
🧩 AIWeave 骨架 · 作者 XuRuibo [email protected] · Apache-2.0 · 模板文件，复制到工程后按业务语义填充
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.
- 8d ago First seen · 74 lines · 30 tokens per session scan A cf1ff4f9f3b9
update-index is a skill published in the GitHub repository zuoyebang/aiweave (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 661 once invoked, about $0.0002 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
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
build-executor
Govern implementation from an approved execution contract. Invoke when execution-contract.md is approved and the user wants disciplined build work, TDD execution, or guarded batch-by-batch implementation.
workflow-start
Primary entry point for the spec-superflow state-machine workflow. Invoke when the user is inside an active spec-superflow change directory (look for .spec-superflow.yaml, changes/ /, proposal.md, specs/, design.md, tasks.md, or execution-contract.md) and asks to start, continue, resume, implement, plan, or figure out…
release-archivist
Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.
bug-investigator
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
contract-builder
Convert approved planning artifacts into an execution contract. Invoke when the user wants to start building, asks to move from planning to implementation, or when execution-contract.md is missing or stale.