agd

Your agentic setup, versioned like a dependency.
Install and update instructions, agents, skills and hooks from git repositories,
without overwriting what your project changed.

Docs · Install · Quick start · How it works · Create a kit

A good agentic setup takes work: AGENTS.md, agents for each role, skills, hooks. You want it in every project, and you want every project to get its improvements. Copies drift, and copying a new version over an old one wipes out what each project changed, so nobody updates.

agd keeps a setup in a git repository, installs it into your projects at a version, and updates it while keeping each project's own changes. The default setup is agentic-defaults; any repository laid out as a source works, and several can share a project.

$ agd init @0.4.0 --with core
Installed agentic-defaults 0.4.0: 25 files from the packs core.
Commit .agd.lock along with the new files.

$ agd status        # weeks later: you chose opus for the reviewer, and edited a skill
agentic-defaults 0.4.0 is installed, and 0.5.2 is available: run agd update.
notes    https://github.com/Zejnilovic/agentic-defaults/releases/tag/v0.5.0
...
update   .claude/agents/developer.md
model    .claude/agents/reviewer.md: opus (kit: sonnet)
edited   .claude/skills/implementation/SKILL.md, newer version available: see agd diff .claude/skills/implementation/SKILL.md, then agd merge or agd reset it
...
new      .claude/skills/session-retro/SKILL.md

$ agd update
...
agentic-defaults is at 0.5.2: 8 updated, 2 added, 0 removed.
Review the changes with git diff, and commit .agd.lock with them.

• Versioned. Sources publish releases as git tags. A project installs one, records it in .agd.lock, and updates with one command, with links to the release notes.
• Plain files in your repository. Your agents read them as they are, people review them in pull requests. No plugin, no runtime, any assistant: Claude Code, GitHub Copilot, Cursor, Codex and others.
• Never overwrites your work. Updates keep an agent's model: and tools: lines and a ## This project section. A file you changed elsewhere is left alone and reported, and agd diff, agd merge and agd reset settle it.
• Composable. Install only the packs you need, and stack your team's setup on top of agentic-defaults.
• Small enough to trust. One bash script that needs only git. It never runs code from a source, and stops with the diff if a source moves a release's tag after you installed it. agd's own releases carry build provenance. See SECURITY.md.

Install

brew install zejnilovic/tap/agd

Without Homebrew, on macOS, Linux, WSL or Git Bash:

curl -fsSL https://raw.githubusercontent.com/Zejnilovic/agd/main/install.sh | bash

The install script puts the latest release in ~/.local/bin; run it again to update. You can also download agd from the latest release, make it executable and put it on your PATH, or run bin/agd from a clone. Install has every way, with checksums and Windows notes, and how to turn on tab completion: source <(agd completion zsh) or bash in your shell's profile; Homebrew sets it up.

Quick start

agd init                               # agentic-defaults' latest release; asks which packs
agd init --with flask,react            # only those packs, and the packs they require
agd init your-org/[email protected]     # another source, at a release; @<commit> works too
agd status                             # what an update would do
agd update                             # move to the latest release
agd uninstall                          # take it all out again; asks about files you changed

Commit .agd.lock with the files, so your team gets the same setup. The quick start walks through a first install, making files your own and a first update.

Commands

-C <dir> works in another folder, --home works in your home folder, for every project on your machine, and --offline uses the cached copy of each source. agd --help lists everything, and the reference has the details.

Learn more

• How agd works: the idea, the words it uses, and what an update does to each file.
• Make installed files your own: project parts, edits, and settling them.
• Keep it up to date, and automatically, with a weekly pull request from CI.
• Mirrors, proxies and offline machines: agd on company networks.
• Combine sources: your team's setup on top of agentic-defaults.
• Install for every project: agd --home init, and the rules for your home folder.
• Create a kit: from an empty repository to a first release, by hand or with the kit-authoring skill.
• Kit sources: the reference for the layout, packs.txt, releases, and agd check before you tag one.
• FAQ, including why not copy the files or use a git submodule.

Contributing

Issues and pull requests are welcome. CONTRIBUTING.md explains how agd is built and tested, and CHANGELOG.md what's coming in the next release.

License

MIT © Sasa Zejnilovic