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 sync-feature-to-docsgit 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/sync-feature-to-docs)<a href="https://agentmods.dev/skills/zuoyebang/aiweave/sync-feature-to-docs"><img src="https://agentmods.dev/badge/skills/zuoyebang/aiweave/sync-feature-to-docs.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.00054 | $0.01882 |
| Opus 5 | $0.00027 | $0.00941 |
| Sonnet 5 | $0.00011 | $0.00376 |
| Haiku 4.5 | $0.00005 | $0.00188 |
Grade A, and why
sync-feature-to-docs 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
把单次需求的代码改动 + 需求设计文档反向同步到全链路 docs/。
公共步骤模板见 skills-spec/01_skill_authoring_guide.md §A-§E。
B1 增量同步场景的核心 Skill。规范见
aiweave/docs-spec/19_incremental_sync_spec.md。
第 0 步：拒绝规则与输入完整性检查
- ⛔ 拒绝（§A.1）：改动触碰
BUILD_STATUS.md§0 中 🚫 模块时立即停止 - 输入完整性检查：
- 缺需求技术文档 → 提示用户补充："本次同步可能遗漏 X 处"
- 缺 git diff / 改动清单 → 提示提供
- PR 跨多个独立特性 → 提示拆分
第 1 步：读输入（公共必读见 §B）
1.1 读取本规范：
- aiweave/PRINCIPLES.md
- aiweave/docs-spec/00..19（全部）
1.2 读取本工程：
- docs/INDEX.md
- docs/BUILD_STATUS.md
- CLAUDE.md（拿到范围判定表）
1.3 读取用户提供：
- 需求技术文档
- git diff / 改动清单 / 关键代码片段
第 2 步：差异分类（按 CLAUDE.md 范围判定表）
| 改动文件 | 影响的 docs/ |
|---|---|
models/{db}/{table}.go |
docs/schema/database_design.md §3.X |
service/{module}/*.go |
docs/service/{module}_service.md + service_design.md |
service/{audit-module}/* |
docs/architecture/audit_log.md |
controllers/http/{audience}/{module}/*.go |
docs/api/{audience}_interfaces.md |
controllers/command/*.go + router/command.go |
docs/service/scheduled_tasks_design.md |
controllers/mq/*.go + router/mq.go |
docs/service/scheduled_tasks_design.md §3 |
middleware/*.go |
docs/architecture/middleware.md |
router/http*.go |
docs/architecture/routing.md |
helpers/*.go（导出 / 全局） |
docs/architecture/helpers_api.md |
helpers/{cache_loaders}.go |
docs/cache/cache_helpers.md |
helpers/kafka.go / kafka_consumer.go |
docs/architecture/helpers_api.md + scheduled_tasks_design.md §3 |
helpers/circuit_breaker.go |
docs/circuit_breaker/circuit_breaker_design.md |
| 涉及 Redis 操作（新 Key / Hash 字段） | docs/cache/cache_design.md §2.X + database_design.md §4 |
components/error.go / service_error.go |
docs/architecture/status_codes.md |
components/constants.go |
docs/architecture/constants.md |
conf/ |
docs/architecture/config.md |
pkg/** |
docs/architecture/pkg_api.md |
test/framework/ |
docs/testing/testing_design.md |
test/cases/ |
对应 docs/api/*.md |
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 · 155 lines · 54 tokens per session scan A 3e1f8a1031cd
sync-feature-to-docs is a skill published in the GitHub repository zuoyebang/aiweave (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 1,882 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
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…
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.
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.
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.