ARCHETYPE
Pragmatist
A balanced, no-drama setup: some rules, some tools, nothing extreme.
Copy this rig
$ git clone --depth 1 https://github.com/Seme4eg/dotfiles MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.
$ curl -fsSL --create-dirs -o .claude/agents/security-reviewer.md https://raw.githubusercontent.com/Seme4eg/dotfiles/master/.config/claude/agents/security-reviewer.md Merge into .claude/settings.json (project) or ~/.claude/settings.json (user). Hook commands reference scripts in the source repo — copy those too.
{
"permissions": {
"deny": [
"Read(./.env)"
]
}
} Subagents (1)
| security-reviewer model: opus | Reviews code for security vulnerabilities |
Hooks (2)
| event | matcher | runs |
|---|---|---|
| SessionStart | * | cat "$HOME"/.config/claude/plugins/cache/karpathy-skills/andrej-karpathy-skills/*/skills/karpathy-guidelines/SKILL.md 2>/dev/null || true |
| Stop | * | say -e 'claude done' |
Plugins (4)
caveman@cavemanandrej-karpathy-skills@karpathy-skillsgopls-lsp@claude-plugins-officiallua-lsp@claude-plugins-official
Permissions
deny (1)
Read(./.env)
ask (0)
—
allow (0)
—
Similar rigs
alipajand/agent-context-doctor
Audit agent context files like AGENTS.md, CLAUDE.md, .cursor/rules/*.mdc, .github/copilot-instructions.md, and prompt docs for quality, safety, contradictions, and repo alignment.
Fort Knox 1.5k tok ·
alipajand/agent-readiness-kit
Audit whether a software repository is ready for AI coding agents (Cursor, Codex, Claude Code, GitHub Copilot, and similar tools).
Fort Knox 1.8k tok ·
caiolombello/claude-dotfiles
—
YOLO Cowboy 1.2k tok ·
alipajand/agent-readiness-action
GitHub Action that scores how ready a repository is for AI coding agents and checks its agent instruction files. Deterministic, no LLM.
Fort Knox 1.2k tok ·