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 commands/ngocsangyem/meowkit/docs-syncgit clone --depth 1 https://github.com/ngocsangyem/MeowKitWhat 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.00000 | $0.00433 |
| Opus 5 | $0.00000 | $0.00217 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
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 2d 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:sync — Living Documentation Update
Usage
/docs:sync
Behavior
Incrementally updates documentation to reflect code changes. Keeps docs in sync with the codebase as a living document. Phase 6 automatically triggers this after feature completion.
Execution Steps
-
Diff against main. Run
git diff main(or the project's default branch) to identify all changed files since the last sync. -
Map changed files to doc sections. For each changed file, determine which documentation section it affects:
- New/changed API endpoint → update
docs/api-reference.md - New/changed component → update
docs/components.md - New/changed service/module → update
docs/modules.md - Changed setup/config → update
docs/setup.md - New ADR → already handled by
/arch, skip
- New/changed API endpoint → update
-
Update affected docs only. For each affected section:
- Read the current doc content
- Read the changed source files
- Update the doc to reflect the new state
- Do NOT rewrite unchanged sections
-
Generate changelog entry if conventional commits exist in the diff:
- Parse commit messages for
feat:,fix:,breaking change:prefixes - Append entry to
docs/changelog.mdwith date and grouped changes - Format:
## [YYYY-MM-DD] ### Features - description (commit-hash) ### Fixes - description (commit-hash)
- Parse commit messages for
-
Verify no stale doc references. Check that:
- No docs reference files/functions/endpoints that no longer exist
- No broken internal links between doc files
- Flag any stale references found
When to Use
- After completing a feature (Phase 6 auto-triggers this)
- Before a release to ensure docs are current
- Periodically during long-running development
Output
Updated documentation files in docs/. Changelog entry if conventional commits detected. List of any stale references found.
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.
- 2d ago First seen · 56 lines · 0 tokens per session scan A bd0258939dbd
docs-sync is a command published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 433 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.