settings — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited settings (Hook) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
A production-ready template for building a Claude Code operating agent. Get an autonomous AI coding assistant up and running in under five minutes — with pre-wired hooks, persistent memory, custom skills, secure permissions, and a complete behavioral framework. Works on macOS, Linux, and Windows.
Stop reinventing CLAUDE.md every time you start a new project. This starter gives you the proven structure — identity, prime directives, memory protocols, tool routing, auto-commit hooks, and command guards — that turns Claude Code from a chatbot into an autonomous operator.
A Claude Code operating agent is a persistent AI assistant configured to manage your development infrastructure. Unlike a generic chatbot, an operating agent:
rm -rf, force pushes, destructive SQL) before they executeThis repository is the starter template — the proven scaffolding that makes all of that work on day one.
git clone https://github.com/psybourg/claude-agent-starter my-agent
cd my-agent
./setup.sh
claudegit clone https://github.com/psybourg/claude-agent-starter my-agent
cd my-agent
.\setup.ps1
claudeThat's it. The setup script verifies your prerequisites, makes hooks executable, initializes git, and prints the plugin install commands to run inside Claude Code.
rm -rf /, git reset --hard, git push --force, DROP TABLE, and other destructive patterns before they execute.github-installer skill that classifies and installs plugins, MCP servers, and standalone tools correctly.settings.json, machine-specific bash allowlist in settings.local.json (gitignored)..env files, SSH keys, cloud credentials, and common secret filenames.docs/.npm install -g @anthropic-ai/claude-codegh auth login)claude-agent-starter/
├── README.md This file
├── CLAUDE.md The agent's brain — customize this
├── CLAUDE.local.md Private notes (gitignored)
├── SECURITY.md What the hooks do and don't protect against
├── setup.sh macOS / Linux / WSL setup
├── setup.ps1 Windows PowerShell setup
├── .gitignore Hardened for secrets
├── LICENSE MIT
├── docs/
│ └── how-to-build-a-claude-code-agent.pdf Full 20-page guide
├── .claude/
│ ├── settings.json Permissions, hooks, enabled plugins
│ ├── settings.local.json.example Local bash allowlist template
│ ├── hooks/
│ │ ├── auto-commit.sh / .ps1 Auto-commit after every response
│ │ └── guard-bash.sh / .ps1 Block dangerous commands
│ ├── skills/
│ │ └── github-installer/ Example skill
│ └── agents/ Custom agent definitions
└── obsidian-memory/
├── Index.md Memory entry point
├── decisions/ Architecture choices
├── mistakes/ What broke + how to fix
├── patterns/ Approaches that worked
├── sessions/ Per-session logs
└── projects/ Per-project contextAfter claude starts, run these slash commands inside the session:
/plugin marketplace add anthropics/claude-plugins-official
/plugin marketplace add anthropics/skills
/plugin marketplace add kepano/obsidian-skills
/plugin marketplace add obra/superpowers-marketplace
/plugin install superpowers@claude-plugins-official
/plugin install code-review@claude-plugins-official
/plugin install document-skills@anthropic-agent-skills
/plugin install skill-creator@claude-plugins-official
/plugin install obsidian@obsidian-skills
/plugin install frontend-design@claude-plugins-official
/plugin install typescript-lsp@claude-plugins-official
/plugin install security-guidance@claude-plugins-official
/plugin install context7@claude-plugins-official
/plugin install double-shot-latte@superpowers-marketplace
/reload-plugins| Approach | Setup time | Memory persistence | Auto-commit | Guard rails | Cross-platform |
|---|---|---|---|---|---|
| Plain Claude Code | 0 min | ❌ None | ❌ Manual | ❌ None | ✅ |
| Custom from scratch | 4–8 hours | ⚠️ Depends | ⚠️ Depends | ⚠️ Depends | ⚠️ Depends |
| claude-agent-starter | 5 min | ✅ Obsidian vault | ✅ Stop hook | ✅ PreToolUse hook | ✅ Bash + PowerShell |
This repository pairs with How to Build a Claude Code Operating Agent — a 20-page PDF that walks through every concept:
A chatbot answers questions in a conversation that resets every time you close the window. A Claude Code operating agent reads instructions from a CLAUDE.md file at session start, maintains persistent memory in an Obsidian vault between sessions, runs tools and shell commands autonomously, dispatches sub-agents for parallel work, and follows the behavioral rules you define. Same underlying model, different configuration.
No. Claude Code uses your Claude.ai subscription (Pro or Max). Run claude after installing the CLI and it walks you through authentication.
Obsidian files are plain markdown on disk. Your agent reads and writes them directly with no special tooling. Wikilinks ([[note]]) automatically track renames. You can browse the vault in Obsidian's GUI for a visual overview. And there are no vendor lock-in concerns — the files work in any markdown editor.
After every Claude Code response, the Stop hook runs git add -A && git commit -m "auto: checkpoint from agent session". This means every step the agent takes is checkpointed. If a session crashes or you close the terminal, your work is committed. You can roll back to any point with git log and git reset.
It intercepts every Bash tool call before execution and exits with code 2 (block) if the command matches any of these patterns: rm -rf /, rm -rf ~, rm -rf *, DROP TABLE, TRUNCATE TABLE, git reset --hard, git push --force, format c:, rd /s /q. It's a safety net — read SECURITY.md for details on what it doesn't catch.
No. The auto-commit hook will fire from both sessions, and the agents will write over each other's changes. One session per project directory. Always.
Yes. The repo includes both bash hooks (for Mac/Linux/WSL) and PowerShell hooks (for native Windows). The Windows setup script automatically rewires settings.json to call the .ps1 versions. WSL2 is still recommended if you can use it — there are fewer edge cases.
You absolutely can, and many people do. This starter saves you the iteration — the structure, hook scripts, permission patterns, gitignore, memory vault layout, and SECURITY notes are all the result of hitting the same problems and learning what works. Clone it, customize the placeholders, and ship.
No. This is an independent open-source project built by Reid Spachman at ixprt. It's compatible with the official Claude Code CLI from Anthropic but not affiliated.
Yes. MIT licensed. Use it however you want. Attribution appreciated but not required.
Before customizing and publishing your own version, read SECURITY.md. It covers what the hooks actually do, what the permission model allows, what's gitignored, and what to audit before making your customized version public.
Found a bug? Have an idea? See CONTRIBUTING.md. PRs welcome.
MIT © Reid Spachman / ixprt
Keywords: claude code, claude-code, ai agent, ai coding agent, autonomous agent, anthropic, llm agent, claude code template, claude code starter, claude code operating agent, claude code skills, claude code plugins, claude code hooks, claude code memory, obsidian memory, agent infrastructure, developer tools, ai development, persistent ai agent, autonomous coding agent, claude.md template, agentic ai, claude code config, claude code setup.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.