AG Kit workflow
A .agents workspace for Google Antigravity: 20 roles, 47 skills, 13 commands, project memory, a safety hook and a CLI with update rollback
- 8,205 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The CLI writes and updates files in the project's `.agents` folder and creates backups next to it
- The kit's commands can run checks, preview servers and deployment in your environment
- The MCP sync script with `--apply` changes settings in the home folder
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add workflows/ag-kitDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI writes and updates files in the project's `.agents` folder and creates backups next to it
- The kit's commands can run checks, preview servers and deployment in your environment
- The MCP sync script with `--apply` changes settings in the home folder
This is third-party code. Review the repository files before installing.
What it does
AG Kit puts a `.agents` folder into a project with everything Google Antigravity needs to work by the rules: six rule files, 20 specialist role definitions (backend-specialist, security-auditor, debugger, orchestrator and others), 47 topic skills and 13 slash commands. Skills load as needed, from api-patterns and database-design to tdd-workflow, vulnerability-scanner and mcp-builder. The commands drive routine processes: `/plan` builds a plan and checklist, `/orchestrate` asks for plan approval, hands work to the roles and verifies the result, `/coordinate` runs independent research in parallel, `/verify` demands proof by running checks. The kit is installed by the `@vudovn/ag-kit` CLI. `ag-kit init` copies `.agents` into a project and merges on a repeat run without touching your files. `ag-kit update` compares three versions of each file (the previous kit version, your local one and the new one), updates clean files on its own, puts conflicts into `.agents/.ag-kit/conflicts/` and makes a backup in `.ag-kit-backups/` first. `ag-kit rollback` restores the latest backup, `ag-kit status` shows the state of the installation. Besides roles and commands, the kit has protection and helper scripts. A `PreToolUse` hook on shell commands blocks only unambiguous destructive patterns: deleting the filesystem root, formatting a drive, overwriting a raw disk. Project memory lives in `.agents/memory`, the `sync-mcp.mjs` script shows and, on command, applies MCP settings with a backup, and `npm run build:antigravity-plugin` builds a local Antigravity plugin with a SHA-256 inventory.
Who it is for. For developers working in Google Antigravity who want a ready set of rules, roles and commands instead of assembling their own `.agents` folder by hand.
Good fit when
- A project is opened in Antigravity and the team needs shared rules, roles and commands
- You want a safe update path for the kit: `ag-kit update --dry-run` first, `ag-kit rollback` if something breaks
- A task should go step by step: `/plan`, then `/orchestrate` with approval and a result check via `/verify`
- The agent needs memory between sessions: agreements and decisions about the project in `.agents/memory`
- You want a simple safety layer against accidentally deleting the root or formatting a drive on a trusted machine
Not a fit when
- You work outside Antigravity: the author guarantees the kit only there, other tools may read the Markdown files but their behavior is not verified
- You need a sandbox: the hook blocks only a narrow list of dangerous commands and does not replace permissions, workspace trust and isolation
- You need one small skill: the kit brings 20 roles, 6 rules and 13 commands, and the whole `.agents` folder has to be tracked
- Node.js 18 or newer is missing: the CLI will not start without it, and the checks inside the repository need Node.js 22
Example request
Install AG Kit in this project and draft a plan for adding authentication with /plan, then let me approve it through /orchestrateLimitations
Support is guaranteed only for Google Antigravity in a trusted workspace. Checks inside the repository need Node.js 22 and Python 3.10 or newer, while the CLI itself runs on Node.js 18. The author warns that the hook blocks only unambiguous patterns and is not a sandbox, so Antigravity permissions and human approval must stay on.
The MCP settings example contains a `YOUR_API_KEY` placeholder: until a key is set, the `check:antigravity` check reports a warning, and strict mode passes only after every placeholder is replaced. The kit includes the penetration-tester role and the red-team-tactics skill built on MITRE ATT&CK; use them only against systems and data you are authorized to test.
The `.agents` folder must not go into `.gitignore`, otherwise Antigravity will not index rules and skills; for local storage the author recommends `.git/info/exclude`. A release counts as production-ready only after a manual smoke test in Antigravity against the list in `PRODUCTION_CHECKLIST.md`. MIT license.
How to disable. Delete the `.agents` folder from the project or restore the earlier state with `ag-kit rollback`. To turn off only the safety hook, set `"enabled": false` in `.agents/hooks.json` and reopen the workspace. The global CLI is removed with `npm uninstall -g @vudovn/ag-kit`.
FAQ
What exactly does the safety hook block?
The hook reads up to 1 MiB of JSON from input, makes no network requests and blocks deleting the filesystem root, formatting a drive and overwriting a raw disk. Ordinary cleanup such as deleting `dist/` or `node_modules/` passes. You can test it by feeding a sample with `rm -rf /`: the command must exit with an error and print `BLOCKED by AG Kit`.
What happens to my edits when I update?
The CLI stores SHA-256 hashes of the original files in `.agents/.ag-kit/manifest.json`. Files changed only by you and your own files stay as they are, clean files are updated, and changes on both sides go to the conflict list with a copy of the new version. A backup is made in `.ag-kit-backups/` before updating unless `--no-backup` is passed.
Do I have to configure MCP right away?
No. `node .agents/hooks/sync-mcp.mjs --check` and `--print` only show the plan and write nothing to the home folder. Applying needs the `--apply` flag and a `suite` or `cli` target; an existing server with the same name is not overwritten without `--force`, and a timestamped backup is made before a file changes.
What do roles do and how do they differ from skills?
A role defines a specialist, for example `frontend-specialist`, `database-architect` or `security-auditor`. A skill supplies topic knowledge, for example `clean-code`, `tailwind-patterns` or `systematic-debugging`, and loads gradually. Routing between them is described by the `request-routing` rule and the intelligent-routing skill.
Can the kit be built into a plugin?
Yes. `npm run build:antigravity-plugin` puts skills, roles, rules, converted commands, the hook and the MCP example into `dist/antigravity-plugin/`, and `PLUGIN_CONTENTS.json` holds the SHA-256 sums. Before installing with `agy plugin install ./dist/antigravity-plugin` the author advises reviewing the contents.
Discussion
No questions or reviews yet.
Related
WorkflowsGoogle's terminal AI agent: edits code across files, runs commands and keeps session history, started with the agy command
A portable .agent folder with memory, skills and protocols that plugs into many coding agents and keeps its knowledge when you switch tools
A multi-agent harness that verifies results by artifacts: stop hooks, an independent judge and an event log for Claude Code, Codex, Cursor and more
Google's CLI and skill set that helps a coding agent build, evaluate and deploy agents on Google Cloud with ADK and Gemini Enterprise
A CLI to run several coding agents: one config, a session console, local memory and a set of engineering skills
A Rust terminal task board: every task runs in its own git worktree and tmux window while Claude Code, Codex, Gemini CLI and other agents work in parallel
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| AG Kit (this entry) | no | 8,205 | |
| Antigravity CLI | yes | 2,662 | the Google Antigravity terminal agent that runs commands and edits code itself; AG Kit adds rules, roles and commands on top |
| OrchestKit | no | 299 | a large plugin for Claude Code and Cursor with skills, specialist roles and quality-check hooks |
| Agent skills setup for AntiGravity | no | 511 | installer of a working setup for Google Antigravity that puts rules |
README in short
The description opens with a capability table: rules and skill discovery, role routing, memory, orchestration, MCP, tool-call protection, packaging, validation. It continues with requirements, a quick start, safe updates with rollback, the built-in Antigravity integration, tables of components and commands and the list of required release checks. The repository holds a migration guide, a security policy with a threat model, a pre-release checklist, a changelog, CLI tests and a documentation site.