Frequently asked questions
Bindry packages agent instructions — Claude Code skills, Codex skills, GitHub Copilot instructions, AGENTS.md, and MCP tools — into reusable, versioned Bindings and Stacks.
What is Bindry?
Bindry is a package manager for AI instructions. Write your team's instructions once — brand voice, sales playbooks, email tone, writing style or coding standards — as reusable Bindings, group them into Stacks, and use them in Claude Code, Codex and GitHub Copilot through plugins, or in any other AI tool through AGENTS.md, Markdown or MCP.
How do I reuse agent instructions across repos?
Write the instruction once as a Binding in Bindry, then either export it as a file (AGENTS.md, or a Claude Code/Codex/GitHub Copilot bundle) into each repo, or install the Claude Code, Codex, or GitHub Copilot plugin so /bindry-sync pulls the Stack into any repo on demand. Either way there is one source, not a copy that can drift.
What's a package manager for SKILL.md?
That's what Bindry is. It versions each Binding, compiles it into a SKILL.md file (Claude Code's on-demand skill format) or the Codex/Copilot equivalent, and re-syncs every consuming repo when the Binding changes — the same job npm or pip do for code dependencies, applied to agent instructions instead.
How do I keep Claude Code and Codex instructions in sync?
Write the instruction once as a Binding in Bindry, then run /bindry-sync from both the Claude Code plugin and the Codex plugin. Each compiles the exact same source content into its own tool's skill format (.claude/skills/ vs .agents/skills/), so there is only one place to edit when the rule changes.
What is AGENTS.md?
A plain-text file listing the instructions an AI coding agent should follow in a repo. It's one of the export targets a Bindry Stack can compile to directly, alongside Claude Code skills, Codex skills, and GitHub Copilot instructions, for tools that read a single instructions file rather than a plugin or skill directory.