Plugin
vardoger
vardoger personalizes Claude Code by analyzing your own conversation history and turning recurring patterns into tailored rules. How it works: the plugin's `analyze` skill calls the `vardoger` CLI, which reads your local `~/.claude/projects/` session files in batches. Claude summarizes each batch for behavioral signals (tools you prefer, libraries you use, coding conventions you follow, mistakes you don't want repeated), then synthesizes the summaries into a single personalization that lands in your rules file. Re-running refreshes the personalization as your history grows. Everything runs on your machine — conversations never leave your disk, there is no server or account, and the output is plain Markdown you can edit or delete. The same CLI also supports Cursor, Codex, and OpenClaw, so the personalization stays consistent across assistants if you use more than one.
- Analysed
- Last observed
What the code does
- Runs hooks automatically Hooks that execute without being called explicitly.
Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.
This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.
Risk
Sign in to see this tool's overall risk level and what drives it. Free.
Coverage
Detailed report
1 finding from automated static analysis of the latest version, with severities and explanations.
Using this tool across your team? We can assess your whole inventory.
Request an inventory assessment