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.
git clone --depth 1 https://github.com/vindm/dotclaudeWrote 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/plugins/vindm/dotclaude/core)<a href="https://agentmods.dev/plugins/vindm/dotclaude/core"><img src="https://agentmods.dev/badge/plugins/vindm/dotclaude/core/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.
<a href="https://agentmods.dev/plugins/vindm/dotclaude/core"><img src="https://agentmods.dev/badge/plugins/vindm/dotclaude/core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dotclaude 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 1mo 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
{
"name": "dotclaude",
"description": "Code review, pre-flight, worktree isolation, guard hooks, and risk-weighted test coverage for Claude Code. Consumed as-is; /dotclaude:coding and /dotclaude:testing elicit your project's bar.",
"version": "3.4.2",
"author": { "name": "Dima Vinokurov" },
"homepage": "https://github.com/vindm/dotclaude",
"repository": "https://github.com/vindm/dotclaude",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 7 skills, 5 agents, 5 hooks travel with it, and installing the plugin installs all of them — 747 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill bootstrap A 0 tokens
- Skill testing A 0 tokens
- Skill worktree A 113 tokens
- Skill coding A 0 tokens
- Skill operating-discipline A 93 tokens
- Skill knowledge-layers A 89 tokens
- Skill decomposition C 80 tokens
- Agent pre-flight A 69 tokens
- Agent product-direction-validator A 82 tokens
- Agent code-review A 65 tokens
- Agent skill-vs-code-audit A 85 tokens
- Agent test-architect A 71 tokens
- Hook Stop A not measured
- Hook PreToolUse A not measured
- Hook SessionEnd A not measured
- Hook PostToolUse A not measured
- Hook SessionStart A not measured
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.
- 1mo ago Changed 2bab89319722
- 1mo ago Changed a4a8787f5d87
- 1mo ago Changed 8804f9535b49
- 1mo ago First seen · 10 lines scan A 490fc11cb6a3
dotclaude is a plugin published in the GitHub repository vindm/dotclaude (1 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
codex-handoff
Three-phase Claude Code Codex CLI collaboration workflow: Claude plans and writes the spec, a Claude subagent implements in the host working tree, a fresh Codex session adversarially reviews the diff. Implementation and review are never the same model. For code changes that deserve a written spec.
robcsaszar-tend
Local, on-demand maintenance skills for SvelteKit + TypeScript repos: security, performance, refactoring, accessibility, and test-coverage scanners that each fix one issue per run and leave the diff for review.
mattpocock-skills
Skills adapted from Matt Pocock's public collection.
xonovex-core
Apply software design, testing, review, version control, credentials, and accessibility practices.
exosuit
Suit up. Build anything. A full engineering organization for Claude Code — deep idea interrogation, TDD sprints, enforced quality gates. 43 skills, 8 agents, 13 hooks, path-scoped rules.
atlas-review
Takes the open pull requests of the Atlas/Bella monorepo from arrival to reviewed, fixed, merged, pushed and reported. The review itself is code-review:code-review, which is read-only, so resolving what it finds is this skill's own stage and the reason it exists. Lands by rebase rather than merge commit, pulls so…