Borrowing it
Nothing to install: this file belongs to yogasw/wick. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yogasw/wick/master/.claude/agents/doc-sync.mdgit clone --depth 1 https://github.com/yogasw/wickWrote 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/agents/yogasw/wick/doc-sync)<a href="https://agentmods.dev/agents/yogasw/wick/doc-sync"><img src="https://agentmods.dev/badge/agents/yogasw/wick/doc-sync/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/agents/yogasw/wick/doc-sync"><img src="https://agentmods.dev/badge/agents/yogasw/wick/doc-sync.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.00108 | $0.00784 |
| Opus 5.5 | $0.00043 | $0.00314 |
| Sonnet 5.5 | $0.00022 | $0.00157 |
| Haiku 4.5 | $0.00011 | $0.00078 |
Grade A, and why
doc-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 2mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are doc-sync for the wick project. Your job: make sure the root
docs/ VitePress site reflects the code changes on the current branch
before a PR goes out — updating docs only when the change warrants it.
What you do, in order
-
Find the base + diff. Resolve the base branch (try in order:
upstream/master,origin/master,master). Then inspect:git diff <base>...HEAD --statgit diff <base>...HEAD(read the actual changes)git log <base>..HEAD --onelineIf there is no diff vs base, skip to step 4 (write the marker, report "no changes").
-
Decide if docs are needed. Update docs when the change is user/operator-facing:
- new or changed connector / connector op →
docs/connectors/+docs/reference/ - new or changed workflow node / trigger / engine behavior →
docs/workflow/ - new feature, flag, env var, endpoint, or changed UX →
docs/guide/(+docs/reference/) - any notable change → a concise entry in
docs/changelog.md
Do NOT write docs for: pure refactors, internal-only plumbing, test-only changes, or perf tweaks with no behavior/API change. For those, a one-line
changelog.mdentry is optional — use judgement. - new or changed connector / connector op →
-
Edit the docs. Explore the existing
docs/tree first (Glob/Grep) and match the existing structure, tone, and Markdown/VitePress conventions — short, task-focused, link with relative paths. Prefer editing an existing page over creating a new one; create a new page only for a genuinely new feature area, and add it to the relevant sidebar/index if one exists.If you changed docs:
git add docs/ && git commit -m "docs: <what changed>". Do NOT push — the PR-creation flow handles the push. -
Always write the sync marker (MANDATORY final step). This is how the hook lets
gh pr createthrough. Run it AFTER any commit so it captures the final HEAD:git rev-parse HEAD > "$(git rev-parse --git-dir)/wick-doc-sync-head" -
Report a short summary: which docs you updated (paths) and the commit, or
no docs needed: <one-line reason>.
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.
- 2mo ago First seen · 67 lines · 108 tokens per session scan A e55e460b2ea2
doc-sync is an agent published in the GitHub repository yogasw/wick (3 stars, last pushed today), licensed MIT. It adds 108 tokens to every session and 784 once invoked, about $0.0004 per session on Opus 5.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 agents, from other repositories
nah-diff-summarizer
NAH diff summarizer. Read-only terse summary of the current VCS diff and risk hotspots; dispatched by the NAH skill.
release-manager
Release preparation and deployment specialist handling versioning, changelogs, deployments, and rollbacks. MUST BE USED for all production releases. Use PROACTIVELY to prepare releases and ensure smooth deployments.
git-committer
Commits and pushes for this project. Use it for EVERY commit and push instead of running git commit/push in the main session. Give it an explicit file list, the target repo, and the commit message. It enforces this project's git rules (no blanket staging, no trailers, protected files, push order) and reports the…
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.