ag-kit

Framework

vudovn/ag-kit

Antigravity-first agent engineering kit with rules, skills, workflows, and safety hooks.

Overview

AG Kit provides a complete workspace contract for building agents on Antigravity. It includes 20 specialist agents, 47 skills, 13 workflows, 6 rules, and a native safety hook. The kit emphasizes safe updates, rollback, and MCP integration.

README Preview

\n  \n\n\nAG KIT\n\n\n  Antigravity-first agent engineering kit with rules, skills, specialist agents, workflows, persistent memory, MCP guidance, orchestration, and a native safety hook.\n\n\n\n  \n  \n  \n\n\n\n  Primary runtime: Google Antigravity\n  Tiếng Việt · Migration guide · Production checklist · Security\n\n\n---\n\n## Production profile\n\nAG Kit installs a complete `.agents/` workspace contract. Antigravity is the supported production runtime for this release. Other tools may read the Markdown components, but runtime behavior outside Antigravity is not part of the production compatibility guarantee.\n\n| Capability | Production implementation |\n| --- | --- |\n| Rules and skill discovery | `.agents/rules/`, `.agents/skills/`, `.agents/workflows/` |\n| Specialist routing | 20 role definitions and intelligent-routing skills |\n| Persistent context | `.agents/memory/` and context-compression guidance |\n| Orchestration | `/coordinate`, `/orchestrate`, Antigravity `/agents` and `/tasks` |\n| MCP | Workspace config plus explicit, backup-aware sync helper |\n| Tool safety | Native `PreToolUse` gate for high-confidence destructive commands |\n| Packaging | Local Antigravity plugin bundle with a SHA-256 content inventory |\n| Validation | Toolkit CI, Antigravity Doctor, regression tests, Dependency Review, CLI and web checks |\n\nThe native hook is deliberately narrow. It blocks root-filesystem deletion, drive formatting, and raw-disk overwrite patterns while allowing normal project cleanup such as deleting `dist/` or `node_modules/`. It does not replace Antigravity permissions, workspace trust, sandboxing, or human approval.\n\n## Requirements\n\n- Node.js 22 or newer for repository-level Antigravity tooling.\n- Python 3.10 or newer for AG Kit validators and utility scripts.\n- A trusted Google Antigravity workspace.\n- Git for safe update, review, and rollback workflows.\n\nThe published CLI currently supports Node.js 18 or newer; the Antigravity integration 

FAQ (2)

Troubleshooting
How to fix 'EIO: Access is denied' when running `npx @vudovn/ag-kit init` or `update` on Windows?

The error occurs because the CLI uses synchronous fs.rmSync() and fs.cpSync() operations on the .agent directory. Windows Defender, IDEs, or file watchers can briefly lock that directory, causing Node.js to fail with EIO, Access is denied.

Fix it by replacing the synchronous filesystem calls with fs-extra's asynchronous methods, which include Windows file-locking retry handling:

import fse from 'fs-extra';

await fse.remove(targetAgentDir);
await fse.copy(sourceAgentDir, targetAgentDir, { overwrite: true });

Make the calling functions async and replace related synchronous checks such as existsSync with:

if (!(await fse.pathExists(sourceAgentDir))) {
  throw new Error(`Could not find ${AGENT_FOLDER} folder in source repository!`);
}

fs-extra is already listed in the package dependencies, so no new dependency is required. As a temporary workaround, close IDEs or terminals watching the project and allow the .agent folder in Windows Defender before rerunning:

npx @vudovn/ag-kit init

GitHub Issue #53
Troubleshooting
Why are Antigravity Kit slash commands missing from the IDE dropdown after installing the .agent folder?

The IDE may ignore slash-command files located in a Git-ignored .agent/ directory. Remove the .agent/ entry from the project's main .gitignore file, then add it locally to .git/info/exclude instead:

1. Delete the .agent/ line from .gitignore.
2. Add .agent/ to .git/info/exclude:

echo ".agent/" >> .git/info/exclude

This keeps .agent/ untracked locally while allowing the IDE to detect /plan, /brainstorm, /debug, and other commands. Reload or restart the IDE if the dropdown does not update immediately.

GitHub Issue #27