conn-castle/agent-layer

A tool for unifying instructions, skills, and MCP servers for various coding agents.

10Stars on the repository
5Mods indexed here, across every type
todayLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

dispatch-agent

01

conn-castle/agent-layer

Skill Claude Code

Use Agent Dispatch MCP tools only when the user names an external dispatch target or another skill explicitly requires dispatch. Do not use it for generic subagent, second-agent, or fresh-context requests; use the built-in subagent instead.

not rated 10 changed 1mo ago A 49 tokens original MIT

skill-sync

02

conn-castle/agent-layer

Skill Claude Code

Manage local skills backed by known remote Git repositories. Use when the user wants to import, inspect, diff, pull, resolve, push, reset, or remove them, or project current local skills to enabled clients with al sync. Do not use to discover new skills or create user-owned skills.

not rated 10 today A 63 tokens original MIT

benchmark

03

conn-castle/agent-layer

Skill Codex

Run A/B tests of skills, instructions, agents, harnesses, and other coding-agent system changes with Agent Layer's DeltaSelect benchmark workflow. Use to select tasks, run or resume a benchmark, interpret score and cost results, or investigate why results changed.

not rated 10 today A 54 tokens original MIT

instruction-sync

04

conn-castle/agent-layer

Skill Claude Code

Manage ordered local and Git-backed Agent Layer instructions. Use for known instruction imports, status, diff, pull, resolve, reset, push, removal, and projection.

not rated 10 today C 36 tokens original MIT

dogfood

05

conn-castle/agent-layer

Skill Claude CodeCodex

Explore Agent Layer through real tasks and inventive experiments in disposable projects; investigate failures, usability friction, and batch fixes. Use for product dogfooding in this repository, excluding skill-content evaluation and A/B benchmarks.

not rated 10 today A 45 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: