Skip to content

Dwg agd-001 · agentic setups

Your agentic setup, versioned like a dependency.

↖ pinned in the lock file, updated when you say so

agd installs instructions, agents, skills and hooks from git repositories into your projects, and updates them without overwriting what you changed.

Get started How it works

No Homebrew? Use the install script, or one download.

Detail A · a session with agd
$ 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.
# Weeks later: you chose opus for the reviewer, and edited a skill.
$ agd status
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 …
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.
$

Works with any assistant that reads files from your repository:
Claude CodeGitHub CopilotCursorCodexGemini CLI

TitleagdSheet1 of 1
DoesInstalls and updates agentic setups
Needsbash 3.2+ · gitLicenseMIT
Runs onmacOS · Linux · Git BashRevlatest ↗

Why agd · general notes

  1. Copy a good agent setup into ten projects, and you have ten setups.
  2. Copy a new version over them, and you wipe out what each project changed.
  3. So nobody updates, and the copies drift apart.

agd keeps a setup in one git repository, installs it into every project at a version, and updates it without touching what each project made its own.

Section A–A · one installed file

The source's lines update. The project's lines stay.

agd records exactly what it installed, so it can tell your changes from the source's. Each installed file has parts that belong to the source, and parts that belong to your project.

  • From the source. agd update replaces it with each release you take.

  • The project's, in red pencil. An agent's model: and tools:, and a ## This project section. Every update keeps them.

  • Anything else you change is an edit, clouded like a revision. agd never overwrites it: diff it, merge it or reset it, your call.

.claude/agents/reviewer.md✓ in .agd.lock
source · updated---
name: reviewer
description: Reviews a change for bugs and broken contracts.
← yours, keptmodel: opus
tools: Read, Grep, Glob
source · updated---

Review the change against its plan. Report each problem
with its file and line, and what would fix it.

- Check that the tests prove the change.
- Flag a contract that changed without a note.
← yours, kept## This project

- Migrations under db/ need a second reviewer.

Parts list · what you get

ItemPartCommands
1

Versioned like a dependency

Sources publish releases as git tags. A project installs one, records it in .agd.lock, and moves on with one command, with links to the release notes.

 agd status
agd update
2

Plain files, in your repository

No plugin and no runtime. Agents read the files as they are, people review them in pull requests, and git keeps their history.

 git diff
3

Never overwrites your work

Edited files are left alone and reported. See both sides of a change, merge the source's changes into yours, or take the source's file.

 agd diff
agd merge
agd reset
4

Take only what you need

Packs group a source's files and bring the packs they require. Add and remove them later, and leave out single files with .agd-ignore.

 agd init --with flask,react
5

Stack setups

Install your team's agents on top of agentic-defaults. Where two sources ship the same path, you choose which one wins.

 agd init your-org/team-kit
6

Small enough to trust

One bash script that needs only git, on macOS, Linux and Windows. It copies files, and never runs code from a source.

 bash 3.2+ · git

Assembly sequence

  1. Install

    agd init copies the latest release of a source into your project, and writes .agd.lock.

  2. Commit

    Commit the files with the lock, so the whole team works with the same setup.

  3. Make it yours

    Pick models, limit tools, add your project's rules. Add agents of your own next to the source's.

  4. Update

    agd status shows what a new release changes; agd update takes it. Your parts stay.

Install it in a minute

brew install zejnilovic/tap/agd

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

curl -fLo ~/.local/bin/agd https://github.com/Zejnilovic/agd/releases/latest/download/agd
chmod +x ~/.local/bin/agd

agd needs bash 3.2 or newer and git, on macOS, Linux, or Windows with Git Bash. Then, in the root of your project:

agd init

That installs agentic-defaults, a setup for Claude Code and GitHub Copilot. Any git repository laid out as a source works: agd init your-org/your-setup.

Quick start All the ways to install

Publish your own setup

Your team's agents, skills and rules can be a source too: a git repository with release tags, and a packs.txt that groups its files. Projects install it alone, or on top of agentic-defaults. Publish your own agentic setup shows how.