portable-agents

To make cross-tool agent prompts portable, write a Markdown file with a standardized YAML frontmatter containing the agent's name and description, followed by the system prompt body, which ensures consistent behavior across Claude Code, Cursor, OpenCode, and Cline.

A portable agent definition is a standardized Markdown file with YAML frontmatter that unifies agent prompts and behavior across multiple development tools, eliminating duplication and configuration drift when reusing agents across different environments.

Yes, you can apply tool-specific overrides to an agent without breaking portability by configuring optional settings like tool restrictions, models, and memory settings, enabling per-tool optimizations while maintaining the shared YAML frontmatter and Markdown body.

Yes, the portable agent format supports tool restrictions and custom model settings. These are configured as optional fields within the portable YAML frontmatter, allowing you to customize agent behavior per tool while maintaining a standardized base.

The best way to prevent configuration drift when porting agents is to use a unified frontmatter format that standardizes the name, description, and system prompt body across tools, ensuring the core agent definition remains consistent across Claude Code, Cursor, OpenCode, and Cline.