getsentry-dotagents

dotagents

Shared tooling for coding agents. Declare skills, MCP servers, hooks, and subagents in agents.toml — dotagents wires them into every agent tool on your team.

Why dotagents?

One source of truth. Skills live in .agents/skills/ and symlink into .claude/skills/ or wherever your tools expect them. Cursor shares Claude-compatible skills. No copy-pasting between directories.

One command to install. agents.toml is committed, managed skills and canonical installed subagents under .agents/ are gitignored. Collaborators run dotagents install to fetch or refresh local agent state.

Shareable. Skills are directories with a SKILL.md. Host them in any git repo, discover them automatically, install with one command.

Multi-agent. Configure Claude, Cursor, Codex, VS Code, and OpenCode from a single agents.toml -- skills, MCP servers, hooks, and subagents where supported. Pi reads .agents/skills/ directly.

Quick Start

npx @sentry/dotagents init

The interactive setup walks you through selecting agents and trust policy. Then add skills:

# Add a skill from a GitHub repo
npx @sentry/dotagents add getsentry/skills find-bugs

# Add multiple skills at once
npx @sentry/dotagents add getsentry/skills find-bugs code-review commit

# Or add all skills from a repo
npx @sentry/dotagents add getsentry/skills --all

This creates an agents.toml at your project root and an agents.lock tracking installed skills and subagents.

After cloning a project that already has agents.toml, run install to fetch skills and subagents. Run it again to refresh managed local state:

npx @sentry/dotagents install

Commands

Command	Description
init	Create agents.toml and .agents/skills/
add <source> [skills...]	Add skill dependencies
remove <name|source> [-y]	Remove a skill or all skills from a source
install	Install all dependencies from agents.toml
list	Show installed skills and their status
sync	Reconcile state offline: adopt local skills, prune stale managed ones, repair configs
mcp	Manage MCP server declarations
trust	Manage trusted sources
doctor	Check project health and fix issues

All commands accept --user to operate on user scope (~/.agents/) instead of the current project.

Source Formats

Skills can come from GitHub, GitLab, any git server, well-known HTTPS skill sources, or local directories:

[[skills]]
name = "find-bugs"
source = "getsentry/skills"              # GitHub shorthand

[[skills]]
name = "review"
source = "getsentry/[email protected]"       # Pinned to a ref

[[skills]]
name = "gitlab-skill"
source = "https://gitlab.com/group/repo" # GitLab URL

[[skills]]
name = "internal"
source = "git:https://git.corp.dev/repo" # Any git server

[[skills]]
name = "error-tracking"
source = "https://cli.sentry.dev"        # Well-known HTTPS source

[[skills]]
name = "local"
source = "path:./my-skills/local-skill"  # Local directory

Shorthand (owner/repo) resolves to GitHub by default. Set defaultRepositorySource = "gitlab" in agents.toml to resolve to GitLab instead.

Agent Targets

The agents field tells dotagents which tools to configure:

agents = ["claude", "cursor", "codex", "opencode"]

Agent	Config Dir	MCP Config	Hooks	Subagents
claude	.claude	.mcp.json	.claude/settings.json	.claude/agents/*.md
cursor	.cursor	.cursor/mcp.json	.cursor/hooks.json	.cursor/agents/*.md
codex	.codex	.codex/config.toml	--	.codex/agents/*.toml
vscode	.vscode	.vscode/mcp.json	.claude/settings.json	--
opencode	.opencode	opencode.json	--	.opencode/agents/*.md

Custom subagents are declared with [[subagents]] entries. dotagents writes generated runtime-specific files during install and repairs them during sync:

[[subagents]]
name = "code-reviewer"
source = "getsentry/agent-pack"
targets = ["claude", "codex", "opencode"]

If targets is omitted or empty, dotagents targets every configured agent and warns for agents that do not support custom subagents.

dotagents discovers portable subagent Markdown from conventional source directories such as agents/ and .agents/agents/. The frontmatter supplies the portable name and description; the body supplies the runtime instructions:

---
name: code-reviewer
description: Review code for correctness, security, and missing tests.
---

Review the current diff and return findings with file references.