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/sabbour/agentweaver/agentweaver-docs-syncnpx skills add sabbour/agentweaver --skill agentweaver-docs-syncgit clone --depth 1 https://github.com/sabbour/agentweaverWhat 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.00040 | $0.00999 |
| Opus 5 | $0.00020 | $0.00500 |
| Sonnet 5 | $0.00008 | $0.00200 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
agentweaver-docs-sync 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 3d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Docs live in docs/ (a VitePress site) and drift from the code as features land. This skill is the repeatable playbook so doc updates are deterministic instead of a one-off prompt. See .github/DOCS_SYNC.md for the full strategy.
Companion skill. This skill owns drift detection and generated/derived docs (the generator + CI check). To author a feature's docs across all facets (deep-dive, reference, user guide, screenshots, landing card, nav, cross-links, diagrams), use the
docs-featureskill. Use them together:docs-featureto write,docs-syncto keep generated docs in sync.
Docs are split into two kinds:
- Generated — derived from source, never hand-edited (carry a
GENERATED — DO NOT EDITheader). - Curated — hand-written prose.
| Surface | Doc | Mode | Source of truth |
|---|---|---|---|
| MCP tools | docs/reference/mcp-tools.md |
Generated | apps/Agentweaver.Mcp/Tools/*.cs |
| MCP tool params | docs/reference/mcp.md |
Curated | hand-written |
| API endpoints | docs/reference/api.md |
Curated | apps/Agentweaver.Api/**/*Endpoints.cs |
| Memory/decisions | docs/reference/memory.md |
Curated | apps/Agentweaver.Api/Endpoints/{Memory,Decisions}Endpoints.cs |
| Blueprints/workflows | docs/guide/workflows.md, docs/reference/* |
Curated | apps/Agentweaver.Api/{Blueprints,Workflows}/, packages/Agentweaver.Squad/Catalog/Resources/blueprints/ |
When to invoke
Invoke this skill whenever a change adds or alters: an MCP tool, an API endpoint, a blueprint, a workflow, or any user-facing feature. The CI workflow .github/workflows/docs-drift.yml also nudges PRs that change these paths without touching docs/**.
Playbook
-
Identify the surface that changed and map it to its doc(s) using the table above.
-
Regenerate generated docs if you touched a generated surface (e.g. MCP tools):
node scripts/gen-docs.mjs # writes docs/reference/mcp-tools.md node scripts/gen-docs.mjs --check # verify in sync (what CI runs)Never hand-edit a generated file — edit the source attribute/route and regenerate.
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.
- 3d ago First seen · 71 lines · 40 tokens per session scan A 59fa81a733b1
agentweaver-docs-sync is a skill published in the GitHub repository sabbour/agentweaver (5 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 999 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-31.
Other skills, from other repositories
auditing-kubernetes-cluster-rbac
Auditing Kubernetes cluster RBAC configurations to identify overly permissive roles, wildcard permissions, dangerous ClusterRoleBindings, service account abuse, and privilege escalation paths using kubectl, rbac-tool, KubiScan, and Kubeaudit.
agent-workflow-playbook
AI Agent Workflow & Skill Architecture Guide — turn expert work into measurable, reusable agent systems. Covers workflow discovery, skill decomposition, harness design, evaluation, human escalation, observability, cost control, and multi-agent orchestration. Includes a measured marketing-delivery case: 15 people × 3–4…
dotnet-microsoft-agent-framework
Build .NET AI agents and multi-agent workflows with Microsoft Agent Framework using the right agent type, threads, tools, workflows, hosting protocols, and enterprise guardrails.
dotnet-microsoft-extensions-ai
Build provider-agnostic .NET AI integrations with Microsoft.Extensions.AI, IChatClient, embeddings, middleware, structured output, vector search, and evaluation.
dotnet-orleans
Build or review distributed .NET applications with Orleans grains, silos, persistence, streaming, reminders, placement, testing, and cloud-native hosting.
mcaf-dotnet
Primary entry skill for C# and .NET tasks. Detect the repo's language version, test runner, quality stack, and architecture rules; route to the right .NET subskills; and run the repo-defined post-change quality pass after any code change. Use when the user asks to implement, debug, review, or refactor .NET code, or…