LifeHubber. Resources Use AI on your terms.
LifeHubber.Resource
Opening…

AI Resources

gitagent

GitHub stars: 754 GitHub forks: 145 Declared license: MIT: MIT Last pushed November 8, 2026: Pushed 10d ago
Stats from GitHub

gitagent keeps an AI agent's configuration, instructions, memory, tools, and skills in a Git repository. It provides a CLI and SDK for running that definition with a configured model provider.

The files describe the agent; the runtime executes its work. Versioning the definition does not make model responses or tool results identical across runs.

What it is

An agent defined in files

agent.yaml holds runtime settings, SOUL.md describes identity, and RULES.md holds behavioral instructions.

Why it stands out

Changes you can compare

Git history lets a team compare rule edits, branch an agent definition, and inspect changes to committed memory.

Availability

CLI, SDK, and documentation

The repository includes installation instructions, configuration examples, and programmatic access to the agent runtime.

Why it matters

What makes it useful

When a team changes how its agent should work, it can review a RULES.md diff instead of passing around a replacement prompt. Memory is also committed to Git, so its history can be examined alongside changes to the definition.

Notable points

What stands out

An agent.yaml definition can extend a base agent from another repository. That gives teams a shared starting definition while keeping a separate agent directory for their own configuration.

Before using

What to review

Agent memory is committed to Git. Check what enters that history before sharing the repository.

The documented repo mode can commit and push work to a session branch; it is more than a read-only repository viewer.

Choose the provider and tool access needed for the task; a versioned rules file is not an execution sandbox.

Check the original listing's documentation for current requirements, limitations, licensing and any relevant privacy or security considerations.

Reader fit

Who may find it relevant

Developers maintaining agent definitions with the same review habits as code.

Teams that want a reusable base definition and visible rule changes.

People willing to configure providers and execution tools.

Editorial note

Why LifeHubber lists it

For a team trying a different supported model provider, the repository can remain the home of the agent's instructions and memory. gitagent keeps the model connection separate from those files. The team can maintain its definition in one place while changing that connection, rather than relocating the instructions into each provider's chat interface.

Source links

Source materials

Reader note

About our listings

LifeHubber’s listings help you explore what’s available in AI and are not endorsements. We don’t independently verify every detail or guarantee that each listing is accurate, safe, actively maintained, or right for your needs.

What to explore next

Keep the work behind the agent reusable.

A Git repository keeps the agent definition readable. The next step is deciding which source files, prompts, decisions, and checks to keep alongside it when you change tools.

Advertisements

Advertisements

For project maintainers

Listed here? You can use the badge.

If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.

MORE ON LIFEHUBBER

Use AI on your own terms.

Explore more AI projects, stories, guides, tools and community insights across LifeHubber.

See what’s moving