zaver

zaver is a command for Claude Code from josefslerka/study-kit. It costs 11 tokens per session (123 once invoked), scanned A, original, MIT.

A process for designing the conclusion of a study. It creates an ending that explains what the reader now knows, opens one or two further perspectives, returns to the introduction’s hook, and states why the result matters.

In plain words
What is it for?
Use it to draft the final section, connect it back to the introduction, state the study’s significance, and choose from three ending sentences.
Why use it?
It prevents the conclusion from being only a summary. It helps give the study a clear final direction and offers several possible last sentences.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

Good fit Use it to draft the final section, connect it back to the introduction, state the study’s significance, and choose from three ending sentences.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/josefslerka/study-kit/zaver
Install

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.

Clone the repo
git clone --depth 1 https://github.com/josefslerka/study-kit

Made for: Claude Code.

Wrote 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.

agentmods badge for zaver

README.md
[![agentmods](https://agentmods.dev/badge/commands/josefslerka/study-kit/zaver/github.svg)](https://agentmods.dev/commands/josefslerka/study-kit/zaver)
Your own site
<a href="https://agentmods.dev/commands/josefslerka/study-kit/zaver"><img src="https://agentmods.dev/badge/commands/josefslerka/study-kit/zaver/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.

agentmods 80×15 button for zaver

Your own site · 80×15
<a href="https://agentmods.dev/commands/josefslerka/study-kit/zaver"><img src="https://agentmods.dev/badge/commands/josefslerka/study-kit/zaver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 123 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.00123
Opus 5.5 $0.00004 $0.00049
Sonnet 5.5 $0.00002 $0.00025
Haiku 4.5 $0.00001 $0.00012

Measured 2mo ago against content hash e2b6e1b4a0c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

zaver 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.

cs/.claude/commands/zaver.md · 9 lines

What it actually says

Proveď bonusovou fázi B.1 dle CLAUDE.md.

Závěr není shrnutí. Navrhni závěr, který: posune čtenáře (věděli jsme X → víme Y), otevře 1–2 perspektivy, vrátí se k háčku z úvodu, dá explicitní „so what" a nabídne 3 varianty poslední věty. Zapiš do study/ jako závěrečnou sekci, zaloguj.

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.

  1. 2mo ago First seen · 9 lines · 11 tokens per session scan A e2b6e1b4a0c2

Subscribe to this mod's changes

zaver is a command published in the GitHub repository josefslerka/study-kit (7 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 123 once invoked, about $0.0000 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.

Related

zaver compared with commands from other repositories

zaver next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
zaverjosefslerka/study-kitCommand74mo agoMITA11Claude Code
checklistgithub/spec-kitCommand148ktodayMITA13Claude Code
clarifygithub/spec-kitCommand148ktodayMITA27Claude Code
specifygithub/spec-kitCommand148ktodayMITA13Claude Code
analyzegithub/spec-kitCommand148ktodayMITA26Claude Code
convergegithub/spec-kitCommand148ktodayMITA35Claude Code
implementgithub/spec-kitCommand148ktodayMITA14Claude Code