Borrowing it
Nothing to install: this file belongs to julianoczkowski/notebooklm-mcp-2026. 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/julianoczkowski/notebooklm-mcp-2026/master/.claude/commands/sync-docs.mdgit clone --depth 1 https://github.com/julianoczkowski/notebooklm-mcp-2026Wrote 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/commands/julianoczkowski/notebooklm-mcp-2026/sync-docs)<a href="https://agentmods.dev/commands/julianoczkowski/notebooklm-mcp-2026/sync-docs"><img src="https://agentmods.dev/badge/commands/julianoczkowski/notebooklm-mcp-2026/sync-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.00000 | $0.00531 |
| Opus 5 | $0.00000 | $0.00266 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
sync-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- sync-docs — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync CLAUDE.md and CHANGELOG.md with recent changes.
Instructions
You are updating the project documentation to reflect the current state of the codebase. Follow these steps.
Step 1: Gather recent changes
Run these in parallel:
git log --onelinefrom the last tagged release to HEAD — to see what changed- Read the current
CLAUDE.md - Read the current
CHANGELOG.md - Read
pyproject.tomlfor the current version
To find the last release tag:
git describe --tags --abbrev=0
Then get commits since that tag:
git log <tag>..HEAD --oneline
Step 2: Scan the codebase for drift
Check if CLAUDE.md is out of date by looking at:
- Commands section — run
grep -r "add_argument\|add_parser" src/to find all CLI subcommands and flags, compare with what CLAUDE.md lists - Architecture section — check if any new modules were added under
src/ - Testing section — check if new test files or markers exist in
tests/ - Repo Structure section — check if any new top-level files or
.github/files exist that aren't listed - Environment Variables — check
config.pyfor any new env vars
Step 3: Propose updates
Show the user a summary of what's out of date:
- What's missing from CLAUDE.md
- What commits should be added to CHANGELOG.md (under an
[Unreleased]section if not yet released)
Ask the user to confirm before making changes.
Step 4: Update CLAUDE.md
Edit CLAUDE.md to reflect the current state. Keep the existing structure and style. Only add or update what's changed — don't rewrite sections that are already accurate.
Step 5: Update CHANGELOG.md
If there are unreleased changes since the last tag, add them under an [Unreleased] section at the top of CHANGELOG.md. Group changes by type:
- Added — new features
- Changed — changes to existing functionality
- Fixed — bug fixes
- Removed — removed features
If there are no unreleased changes, skip this step.
Step 6: Commit
git add CLAUDE.md CHANGELOG.md
git commit -m "Sync docs with recent changes"
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 · 64 lines · 0 tokens per session scan A 5f7aafc5c174
sync-docs is a command published in the GitHub repository julianoczkowski/notebooklm-mcp-2026 (16 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 531 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
improve
Run ONE iteration of the continuous-improvement loop — pick the highest-value backlog item, implement it, verify end-to-end, commit.
commit
Analyze changes and create atomic, conventional commits with intelligent message generation, version management, changelog updates, and quality insights.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.
triage-github
Scan GitHub repos for activity, generate a summary, and create actionable GTD tasks.