Agent Compat Sync logo

Agent Compat Sync

Community
wquguru
agent-compat-sync

Keep repository-level Claude and Codex agent instructions compatible by creating safe symlinks between CLAUDE.md and AGENTS.md, and between .claude/skills/* and .agents/skills/*. Use when a repository should work with both Claude and Codex, when one agent instruction file exists but the other is missing, when migrating agent skills between .claude and .agents directories, or when asked to improve Claude/Codex compatibility for a repo.

Overview

Publisherwquguru
Repositoryskills
Skill nameagent-compat-sync
Stars
94
Forks
7
Bundled files
2
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by wquguru on GitHub. Read the source before you install it.

Installation

Install the Agent Compat Sync AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/wquguru/skills/tree/main/skills/agent-compat-sync
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/wquguru/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/agent-compat-sync .claude/skills/agent-compat-sync
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Agent Compat Sync in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Agent Compat Sync on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Agent Compat Sync is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Agent Compat Sync

Make a repository usable by both Claude and Codex without duplicating instruction files or skill folders. Prefer symlinks so one canonical source stays authoritative.

Workflow

  1. Inspect the repository root for CLAUDE.md, AGENTS.md, .claude/skills, and .agents/skills.
  2. Choose the canonical side:
    • If CLAUDE.md exists and AGENTS.md is missing, treat Claude as canonical.
    • If AGENTS.md exists and CLAUDE.md is missing, treat Codex as canonical.
    • If one instruction file is already a symlink to the other, treat the real target side as canonical.
    • If both instruction files exist as independent real files, stop and ask the user which file should become canonical.
  3. Create the missing instruction-file symlink:
    • Claude canonical: AGENTS.md -> CLAUDE.md
    • Codex canonical: CLAUDE.md -> AGENTS.md
  4. Mirror skill entries with per-entry symlinks:
    • Claude canonical: create .agents/skills/<name> -> ../../.claude/skills/<name> for each item in .claude/skills.
    • Codex canonical: create .claude/skills/<name> -> ../../.agents/skills/<name> for each item in .agents/skills.
  5. Treat an existing path as acceptable when it already resolves to the same real target, even if the symlink is on a parent directory or points in the reverse direction.
  6. Never overwrite existing real files or directories without explicit user approval. Report conflicts with exact paths.

Scripted Sync

Use the bundled script for normal execution:

bash
python3 scripts/sync_compat.py --repo /path/to/repo

From the target repository root, this is also valid:

bash
python3 /path/to/agent-compat-sync/scripts/sync_compat.py

Useful options:

  • --dry-run: show planned changes without writing.
  • --repo PATH: run against a repository other than the current working directory.

The script is intentionally conservative. It creates missing symlinks and directories, leaves correct or equivalent symlinks alone, and exits non-zero when it finds ambiguous or conflicting existing paths.

Manual Fallback

If the script cannot be used, apply the same rules manually with relative symlinks.

Claude canonical:

bash
ln -s CLAUDE.md AGENTS.md
mkdir -p .agents/skills
ln -s ../../.claude/skills/<skill-name> .agents/skills/<skill-name>

Codex canonical:

bash
ln -s AGENTS.md CLAUDE.md
mkdir -p .claude/skills
ln -s ../../.agents/skills/<skill-name> .claude/skills/<skill-name>

Before creating any symlink manually, check whether the destination already exists. If it exists and is not already the expected symlink, stop and ask the user.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Agent Compat Sync AI skill do?

Keep repository-level Claude and Codex agent instructions compatible by creating safe symlinks between CLAUDE.md and AGENTS.md, and between .claude/skills/* and .agents/skills/*. Use when a repository should work with both Claude and Codex, when one agent instruction file exists but the other is missing, when migrating agent skills between .claude and .agents directories, or when asked to improve Claude/Codex compatibility for a repo.

Why use Agent Compat Sync on TypingMind?

Because you install it once and use it with any model. Agent Compat Sync is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Agent Compat Sync in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/wquguru/skills/tree/main/skills/agent-compat-sync. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Agent Compat Sync?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Agent Compat Sync?

As many as you like. As long as a model supports skills, you can use Agent Compat Sync with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Agent Compat Sync AI skill free?

It is published on GitHub by wquguru. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇