Borrowing it
Nothing to install: this file belongs to kkaminsk/NotebookLM-MCP. 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/kkaminsk/NotebookLM-MCP/main/.claude/commands/openspec/archive.mdgit clone --depth 1 https://github.com/kkaminsk/NotebookLM-MCPWrote 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/kkaminsk/notebooklm-mcp/archive)<a href="https://agentmods.dev/commands/kkaminsk/notebooklm-mcp/archive"><img src="https://agentmods.dev/badge/commands/kkaminsk/notebooklm-mcp/archive.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.00015 | $0.00267 |
| Opus 5 | $0.00008 | $0.00133 |
| Sonnet 5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
OpenSpec: Archive 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 6d 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
2 near-identical copies found in the catalogue:
- archive — 100% identical, 0 lines differ
- OpenSpec: Archive — 100% identical, 0 lines differ
What it actually says
Guardrails
- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
- Keep changes tightly scoped to the requested outcome.
- Refer to
openspec/AGENTS.md(located inside theopenspec/directory—runls openspecoropenspec updateif you don't see it) if you need additional OpenSpec conventions or clarifications.
Steps
- Identify the requested change ID (via the prompt or
openspec list). - Run
openspec archive <id> --yesto let the CLI move the change and apply spec updates without prompts (use--skip-specsonly for tooling-only work). - Review the command output to confirm the target specs were updated and the change landed in
changes/archive/. - Validate with
openspec validate --strictand inspect withopenspec show <id>if anything looks off.
Reference
- Inspect refreshed specs with
openspec list --specsand address any validation issues before handing off.
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.
- 6d ago First seen · 22 lines · 0 tokens per session scan A 3d5013a41299
OpenSpec: Archive is a command published in the GitHub repository kkaminsk/NotebookLM-MCP (2 stars, last pushed 8mo ago), licensed MIT. It adds 15 tokens to every session and 267 once invoked, about $0.0001 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 commands, from other repositories
OpenSpec: Archive
Archive a deployed OpenSpec change and update specs.
OpenSpec: Archive
Archive a deployed OpenSpec change and update specs.
OpenSpec: Archive
Archive a deployed OpenSpec change and update specs.
OpenSpec: Apply
Implement an approved OpenSpec change and keep tasks in sync.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
update-docs
Research the current dhpk implementation and update user or agent docs without changing source semantics.