Use when adding support for a new AI coding agent to Gryph, or when changing how an existing agent adapter is wired. Trigger this whenever the user wants to integrate a new agent (for example Claude Code, Cursor, Gemini, Codex, Windsurf, or any other tool), add a new adapter package under agent/, wire agent hook events, or asks how adapters detect, install hooks, parse events, or register. Also trigger on phrases like "add a new agent", "support agent X", "new adapter", or "hook up agent X to...
Installs into .claude/skills of the current project.
Are you the author of Add Agent Adapter?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/safedep-add-agent-adapter)
---
name: add-agent-adapter
description: Use when adding support for a new AI coding agent to Gryph, or when changing how an existing agent adapter is wired. Trigger this whenever the user wants to integrate a new agent (for example Claude Code, Cursor, Gemini, Codex, Windsurf, or any other tool), add a new adapter package under agent/, wire agent hook events, or asks how adapters detect, install hooks, parse events, or register. Also trigger on phrases like "add a new agent", "support agent X", "new adapter", or "hook up agent X to gryph", even when the user does not say the word "adapter".
---
# Add a New Agent Adapter
The full, current guide is `docs/agent-adapter.md`. It is the single source of truth for this task. Read it and follow it step by step.
Do not add an agent adapter from memory. The adapter pattern touches several files across `agent/`, `config/`, `cli/`, and `tui/`. A missed file breaks detection, registration, or the security response path. The doc lists every file and the exact change each one needs.
## How to use this skill
1. Read `docs/agent-adapter.md` in full.
2. Follow each step in order. Use the wiring table in the doc to change every listed file.
3. Use an existing adapter as your reference. The `agent/gemini/` package is the recommended model for the `settings.json` pattern.
4. Run the verify commands from the doc's final step before you finish.
## Invariants
The doc explains these. They break silently if you miss them.
1. Implement `HookConfigPaths()` and return a glob for every file the install step writes. Self-protection guards only these paths. `TestAdapters_InstallWritesOnlyDeclaredHookConfig` fails when a written file has no glob.
2. Implement `Hooks()` with one `events.HookSpec` per hook, including its phase. The decision service reads the phase from it. Regenerate `docs/agent-enforcement-coverage.md` with `GRYPH_UPDATE_DOCS=1 go test ./cli -run TestEnforcementCoverageDoc`.
3. Keep agent knowledge in the adapter package. Do not add agent paths, file names, or command regexes to `aarm/loader` or `aarm/pdp`. The loader derives the shell-command check from the declared paths, and `aarm/shellcmd` parses commands with `mvdan.cc/sh`. Do not match shell commands with a regex.
4. Register the adapter only in `registerAdapters` in `cli/root.go`. The self-protection globs come from that list.
5. Self-protection is best effort. Do not describe it as a security boundary. Kernel-based self-protection is on the roadmap.
## Keep the doc correct
The doc is the source of truth, so keep it accurate. If you find the code no longer matches the doc, update `docs/agent-adapter.md` in the same change. Do not fork the guidance into this skill.
