← ClaudeAtlas

personal-agent-config-kitlisted

Synchronize a single developer's verified agent instructions and bounded preferences across local workstations and repositories. Use when setting up, publishing, syncing, inspecting, rolling back, or recovering Personal Agent Config Kit state.
verivus-oss/llm-cli-gateway · ★ 15 · AI & Automation · score 80
Install: claude install-skill verivus-oss/llm-cli-gateway
# Personal Agent Config Kit Use the Kit for one developer who wants the same personal agent baseline on multiple workstations and repositories. It is a local, Git-synchronized personal configuration layer, not an organization, team, tenancy, or remote policy service. Read [the Kit guide](../../../docs/guides/PERSONAL_AGENT_CONFIG_KIT.md) before changing the baseline or recovering an interrupted attempt. ## Enable and bootstrap Configure each workstation's local gateway: ```toml [personal_config] enabled = true baseline_path = "~/.agent-config" max_stale_hours = 168 ``` `baseline_path` must resolve to a non-home, non-symlinked descendant of the current user's home directory. Relative paths, `/`, `~`, `..` traversal, and existing symbolic-link components are rejected before permission hardening. Use a private Git remote. `config_init` accepts an HTTPS URL without userinfo, authenticated through the normal Git credential helper, an SSH URL without a password authenticated through the normal SSH agent, or standard SSH shorthand. It rejects local paths, plaintext `git://`, helper transports, URL credentials, query or fragment components, and dash-leading hosts. ```text config_init({remote:"git@github.com:you/agent-config.git"}) ``` For a new baseline, initialize it, use ordinary Git tooling to add a remote and first commit, then publish. Do not put secrets, tokens, `.env` files, or machine binding data in the baseline. ## Synchronization workflow 1. Edit and commit the